This a quick follow-up to this question... I couldn't determine the reasons why this JIRA [1] was marked as Resolved, so I have re-opened the JIRA. I know that doesn't help your immediate problem, but at least it's an open, known problem again...
Kevin [1] https://issues.apache.org/jira/browse/OPENJPA-459 On Thu, Oct 22, 2009 at 8:38 AM, Kevin Sutter <[email protected]> wrote: > Hi amitm, > Hmmm... This is confusing. The OPENJPA-459 JIRA is marked as Resolved, > but there are no Commits or Comments indicating it was fixed by this JIRA or > any other JIRA. I'll try to check into it and see what the scoop is. > > Sorry for the confusion, > Kevin > > > On Thu, Oct 22, 2009 at 4:12 AM, amitm <[email protected]> wrote: > >> >> Hi All, >> I am facing a problem in JPQL update query. There is already a bug >> reported as OPENJPA-459. As I am using OpenJpa jar version as 1.2.1. and >> the >> fix version of OPENJPA-459 is 1.2.0 still I am facing this problem. >> >> By configuring following settings in persistence.xml, it worked fine. But >> doing so restrict using sub-select queries anywhere in the application. >> <property name="openjpa.jdbc.DBDictionary" >> value="mysql(SupportsSubselect=false)" /> >> >> Can anyone suggest any fix for this problem? >> >> Thanks, >> amitm >> -- >> View this message in context: >> http://n2.nabble.com/Problem-with-bulk-updates-in-mySQL-tp3871180p3871180.html >> Sent from the OpenJPA Users mailing list archive at Nabble.com. >> > >
