Re: Positional Parameters with update query

2011-11-01 Thread Kevin Sutter
Hi Prashant, Mike can correct me if I'm wrong, but I believe the non-sequential positional parameter detection is due to the sub-select. Since your query has a sub-select "(SELECT x.p1 FROM Binder x WHERE x.p1=?2)", the processing for the parameters starts over as if it's a new Select. Since only

Re: Positional Parameters with update query

2011-11-01 Thread Prashant Bhat
Hi Mike, The query works with this compatibility option. The issue OPENJPA-1999 is for non-sequential positional parameters, but in this query, parameters are specified in correct sequence. So IMO this should be enabled by default. I've set thi

Re: Positional Parameters with update query

2011-10-31 Thread Michael Dick
Hi Prashant, This sounds like OPENJPA-1999. Can you try adding the compatibility option to enable non sequential parameters? Here's the relevant property for persistence.xml : -mike On Sun, Oct 30, 2011 at 7:32 AM, Prashant Bhat wrote: > Hi,

Positional Parameters with update query

2011-10-30 Thread Prashant Bhat
Hi, When positional parameters are used with IN (select ...) query as in the below test case, OpenJpa throws an error that "JPQL positional parameters must start at 1". The same query with named parameters works. openjpa-persistence-jdbc/src/test/java/org/apache/openjpa/persistence/jdbc/query/Tes