Hi, In version 1.1.x, the optimization for IN(SELECT...) is enabled by default, while it was disabled in version 1.0.x. So far I couldn't find a problem. Could you post some more details please (the query, the tables, the indexes)? Or if possible, could you post a reproducible test case?
To disable the optimization, set the system property h2.optimizeInJoin to false before loading the H2 JDBC driver. Regards, Thomas On Fri, Oct 10, 2008 at 5:19 AM, Prashant Bhat <[EMAIL PROTECTED]> wrote: > > Hi Thomas, > > I've been using H2-1.0.79 with OpenJPA-1.1.0 and it works without any > issues. But when I update to H2-1.1.100, WHERE ... IN(SELECT ...) is > not returning any objects! The Sql generated by OpenJPA is correct as > I've tried executing it in H2Console wherein it works. And I noticed > that, it works if the database was created using 1.0.79 , but if I > again create/update the database(with 1.1.100) using MappingTool, it > doesn't work any more. > > Should there be any changes to H2Dictionary? > > Tomorrow, I'll try to find out more about this and 'll post the > details. > > Regards, > Prashant > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/h2-database?hl=en -~----------~----~----~----~------~----~------~--~---
