> > > Order By: ... issues if used in a subquery > > I can't see any reason why an ORDER BY would be necessary in a sub- > query > > The sub-query returns a set and sets (tables) aren't sorted. You > wouldn't sort on a "regular" table that you join on either. > Even with an IN or EXISTS operator the ORDER BY does not make sense.
Hi Thomas, well in this case it actually does make sense, besides that the query is formally correct and should compile. The idea on "ORDER BY sub.ismldef LIMIT 1" is to get entries flagged as default language first. And I didn't know that such sets are not sorted - we tested this on MySQL and they were (or at least appeared to). But thats no real problem at all even if the set is not sorted ... I implemented a workaround involving IF's for H2 to get the expected behaviour. Cheers, Markus --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
