Since this error was showing up in a very limited number of cases, we dug into our query generator and found this type outer join condition referencing a table within an enclosed inner join, was being added to the ON clause for perhaps the no-longer valid reason of helping Oracle to choose an optimal query plan. It was so long ago, and the fact we will be using Oracle 11 with this version of our product, that we decided to remove the logic that was adding this restriction, and wait and see what happens when we do performance testing on Oracle, which is several months away. The queries compile fine on H2.
In short, our immediate need for a fix has gone away. We hope we don't need to put this logic back in. If you come up with a fix for H2 in the meantime, then this potential switch back will be painless. If we never need to put it back in, and you never fix it, then we will probably never care. On Nov 10, 10:39 am, Wes Clark <[EMAIL PROTECTED]> wrote: > Please keep us posted on your progress. We want to take the newer > version for the Oracle-compatible handling of NULLs in an index. > > On Oct 30, 10:44 am, "Thomas Mueller" <[EMAIL PROTECTED]> > wrote: > > > > > I'm not sure if the result and the performance of version 1.0.62 is > > correct in every case. As I wrote, it is a bug, and I will try to fix > > it, but it is complicated to implement correctly. > > > Regards, > > Thomas > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
