#idempiere IRC log for Monday, 2015-11-02

*** mbozem has joined #idempiere02:34
*** a42niem has joined #idempiere06:20
*** mbozem has quit IRC06:35
Not-33c0[IDEMPIERE] tsvikruha updated IDEMPIERE-223006:50
Not-33c0[IDEMPIERE] [~carlosruiz_globalqss] that's the case why we needed ViewID (IDEMPIERE-1970). This could be used also in this case but question is how? I also met something similar while testing IDEMPIERE-2709.06:51
Not-33c0[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-223006:51
*** mbozem has joined #idempiere07:17
*** KermitTheFragger has joined #idempiere07:32
*** BizU has joined #idempiere08:43
BizUhi all, let me to discuss idmepiere08:44
*** nmicoud has joined #idempiere09:11
*** nmicoud has quit IRC10:17
*** mbozem has quit IRC10:33
*** nmicoud has joined #idempiere10:35
*** hieplq has joined #idempiere10:51
*** mbozem has joined #idempiere10:57
*** nmicoud has quit IRC11:08
*** a42niem has quit IRC11:14
*** hieplq has quit IRC11:22
*** hieplq has joined #idempiere11:24
Not-33c0[IDEMPIERE] hieplq updated IDEMPIERE-2907 status set to "Reopened" -resolution set to "None"11:28
Not-33c0[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-290711:28
Not-33c0[IDEMPIERE] hieplq updated IDEMPIERE-2907 Attachment set to "IDEMPIERE-2907-MF.patch"11:28
Not-33c0[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-290711:28
Not-33c0[IDEMPIERE] hieplq updated IDEMPIERE-290711:31
Not-33c0[IDEMPIERE] [^IDEMPIERE-2907-MF.patch] is patch for below warning in eclipse or build by headless "Version '7.0.7.qualifier' of plug-in 'org.zkoss.zk.library' is not available."11:31
Not-33c0[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-290711:31
Not-33c0[IDEMPIERE] hieplq updated IDEMPIERE-2907 status set to "Peer Review Queue"11:31
Not-33c0[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-290711:31
*** a42niem_ has joined #idempiere12:10
*** hieplq has quit IRC13:26
*** hieplq has joined #idempiere13:27
*** CarlosRuiz has joined #idempiere15:09
*** ChanServ sets mode: +o CarlosRuiz15:09
Not-33c0[IDEMPIERE] dantam created IDEMPIERE-2921 Restrict service products from being delivered when items are back ordered15:09
Not-33c0[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-292115:09
*** mbozem has quit IRC16:31
*** norbertbede has joined #idempiere16:35
norbertbedehi CarlosRuiz16:36
norbertbedewant to ask a conceptual question16:36
norbertbedewe need to decide it is important or not for communitz16:36
norbertbedewe need time to time in warehouses use pricelist fboth for sales and purchase side16:36
norbertbedethis way we want improve Pricelist from issotrx to list sales/purchase/both16:37
norbertbedewdyt16:37
norbertbedeif no community interest we made customisation16:37
*** BizU has quit IRC16:39
*** hieplq has quit IRC16:45
CarlosRuizHi norbertbede - I think that's better to ask in forums16:52
*** mbozem has joined #idempiere16:56
norbertbedeok thanks16:59
*** KermitTheFragger has quit IRC17:02
CarlosRuizI added some time ago the SO/PO/Both list on dictionary - for payment terms I think - so it would be like using that one for price lists - let's see what community think about it17:10
norbertbedei created a thread17:13
norbertbedewell17:13
norbertbedethanks anyway17:13
norbertbedelet me ask one more question17:14
norbertbedesetup.ini is config where i can add more jvm parameters ?17:15
norbertbedecant find wiki for this17:15
CarlosRuizif you start with "idempiere" - I think it read parameters from setup.ini17:16
CarlosRuizbut if you start with idempiere.sh you can add the parameters right there17:16
CarlosRuizI usually add them directly on idempiere.sh17:16
norbertbedeok thanks17:18
norbertbedei bit unconfortable if i have lot jvm parameters in one long line :)17:19
*** xapiens has joined #idempiere17:26
*** mbozem has quit IRC17:29
*** xapiens has quit IRC17:29
*** a42niem_ has quit IRC17:51
*** ChuckBoecking has joined #idempiere18:13
ChuckBoeckingHi Carlos, you have a moment to discuss https://idempiere.atlassian.net/browse/IDEMPIERE-279818:18
ChuckBoeckingI am trying hard to understand.18:18
ChuckBoeckingHi CarlosRuiz, you have a moment to discuss https://idempiere.atlassian.net/browse/IDEMPIERE-279818:26
CarlosRuizHi ChuckBoecking18:26
ChuckBoeckingsorry for the double tab. I did not know if addressing you as Carlos (not CarlosRuiz) would notify you.18:27
CarlosRuizno, just the second18:27
ChuckBoeckingcool.18:27
ChuckBoeckingSo, reviewed the linked ticket and discussion. I feel like I understand the issue and the fix for that scenario.18:27
ChuckBoeckingI feel like I undestand the MRole.getAccessSQL() method18:28
ChuckBoeckingIf I read it correctly, the " WHERE " drives whether you add a "where" or "and". I am struggling to see how using "WHERE" phase turns it off. Can you give me a code line hint?18:30
ChuckBoeckingthank you for your time and patience on this matter18:31
CarlosRuizChuckBoecking, I don't understand why you see this as an issue  :-)19:02
ChuckBoeckinggood question -19:03
CarlosRuizin some cases (like in the link I pointed in forums - virtual column)  the MRole.getAccessSQL parses wrongly the SQL and output a wrong one19:03
ChuckBoeckingA user what trying to limit the results of a window by using the tab's where clause. He could not figure out why it was not working19:03
CarlosRuizthat's not a tool for users19:04
ChuckBoeckingHe was in the habit of always using upper case key words19:04
ChuckBoeckingwhen I say user, I mean admin.19:04
CarlosRuizok - then I would expect admins to be a littlemore saviour   ;-)19:04
CarlosRuizand I guess admins can expect a better documentation  :-)  our fault19:04
ChuckBoeckingthat is where I do not understand. I have used the where clause for years.19:04
CarlosRuizso - that's why in the end I see this as a documentation problem19:04
CarlosRuizthe workaround in such case is that simple - put where in lowercase when you don't want that part to be touched19:05
ChuckBoeckingthat makes sense19:05
CarlosRuizlook here for the real case where that happened19:05
CarlosRuizhttps://groups.google.com/d/msg/idempiere/QNo2VukHDBM/8j0059Ikj-kJ19:05
ChuckBoeckingsince you said there are times where it does make sense to have an upper case where, I am trying to find that scenario.19:05
ChuckBoeckingI cannot find one where the system would make any intelligble decision.19:06
CarlosRuizmost of the cases I write where in uppercase19:06
CarlosRuizjust move to lowercase when the AccessSqlParser is broken19:06
ChuckBoeckingthat - I undestand19:06
ChuckBoeckingso here is my question...19:07
ChuckBoeckingAre there other key words (such as FROM, SELECT) what the AD_Tab.WhereClause depends on?19:07
ChuckBoeckingwhere case matters...19:08
CarlosRuizI guess there must be - but haven't checked19:08
ChuckBoeckingOnce I started going down the rabbit hole, I was looking for a valid reason have an upper case.19:08
ChuckBoeckingEspecially since the rest of the system like it when you do use upper case for key words.19:09
CarlosRuizmy "rule of thumb" is like this -> write reserved words in uppercase everywhere19:09
CarlosRuiztest19:09
CarlosRuizif you get the AccessSqlParser.getTableInfo: More than one FROM clause19:10
CarlosRuizthen move the offending where to lowercase19:10
CarlosRuizthat's my way of coping with that19:10
ChuckBoecking:)19:10
ChuckBoeckingI can deal with that...19:10
ChuckBoeckingwhere should I document that wisdom?19:10
ChuckBoeckingin whereClause AD?19:11
CarlosRuizdon't know - maybe a "Tips and Tricks" space -19:11
ChuckBoeckingOK - I will close the ticket as such.19:13
CarlosRuiz:-)   JJ coping with similar scenario19:13
CarlosRuizhttps://sourceforge.net/p/compiere/bugs/2038/19:13
CarlosRuizfunny answer at the end - in the end again -> it's a lack of documentation19:14
ChuckBoeckingI think what cause the issue is the 'bypass'. I though that you were saying you could by pass it as in turn it off. I now understand that you mean "does not get caught by".19:14
ChuckBoeckingthanks again for your time and patience :)19:15
CarlosRuiznp - gr8 if you can document it somewhere - so next time we just refer people there  :-)19:16
Not-33c0[IDEMPIERE] cboecking updated IDEMPIERE-2798 description set to "UPDATE: Closing this ticket as a documentation issue. Here are the comments/advice moving forward: * Generally speaking, admins should use upper case when writing SQL key words. * There are times when iDempiere's is not capable parsing the SQL correctly when admins inject SQL in ColumnSQL or WhereCause fields. This ticket represents an example. Others19:47
Not-33c0are listed below. * You can identify this situation by reviewing the logs and reading the resulting SQL generated by the parser. Error results might include "More than one FROM clause", or you receive a SQLException. * The solution is to make your SQL keywords lowercase, and therefore prevent your clause from being caught in the SQL Parser. ----------------- Original Post ----------------- Using the word "WHERE" in19:47
Not-33c0upper case in the AD_Tab => whereClause field causes a SQL exception because of a poorly formed SQL statement. Here is how to reproduce. Add the following to the Sales Order window's Sales Order Line tab's where clause: C_Order_ID in (Select o.C_Order_ID from C_Order o WHERE o.C_Order_ID = @C_Order_ID@) This will cause a SQL exception. If you make the "WHERE" word lowercase, the all works as expected. The easy19:47
Not-33c0solution is to modify the MTab.getWhereClause() to return a .lower version of the string. If you want to investigate further, set a break point at GridTable line 410 where it executes the MRole.addAccessSQL. Here is an example of the malformed SQL. See the bolded text. SEVERE: Count SQL=SELECT COUNT(*) FROM C_OrderLine WHERE ((C_Order_ID in (Select o.C_Order_ID from C_Order o WHERE o.C_Order_ID = 1000000)) AND19:47
Not-33c0C_OrderLine.C_Order_ID=1000000) AND C_OrderLine.AD_Client_ID IN(0,11) AND C_OrderLine.AD_Org_ID IN(50007,0,50004,50005,50006,50000,50001,50002,11,12) AND (*WHERE.C_OrderLine_ID* IS NULL OR WHERE.C_OrderLine_ID NOT IN ( SELECT Record_ID FROM AD_Private_Access WHERE AD_Table_ID = 260 AND AD_User_ID <> 100 AND IsActive = 'Y' )) Please review. If you agree with my assessment, just let me know and I can make the patch to19:47
Not-33c0make the whereClause getter return lower case. Regards, Chuck Boecking www.chuckboecking.com"19:47
Not-33c0[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-279819:47
Not-33c0[IDEMPIERE] cboecking updated IDEMPIERE-2798 status set to "Closed" -assignee set to "Chuck Boecking" -resolution set to "Won't Fix"19:49
Not-33c0[IDEMPIERE] Closing as a documentation issue.19:49
Not-33c0[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-279819:49
*** nmicoud has joined #idempiere21:04
*** nmicoud has left #idempiere21:11
*** norbertbede has quit IRC21:48
*** norbertbede has joined #idempiere21:48
*** mbozem has joined #idempiere21:49
*** mbozem has quit IRC22:06
*** CarlosRuiz has quit IRC22:41

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!