Hi, > I'm almost sure the conversion order is defined in the SQL standard > (but I don't know where).
If that is really SQL standard, then the case is solved, as inspector Clouseau used to say :) > > Then maybe a better way would be to throw an > > error if compatibility mode is set on. > > That's possible, but is this really necessary? What is the use case? > Emulating all features of all databases would be too much work. My > plan is to only support compatibility for the most important features. I generate SQL statement from the user input using some kind of meta programing techniques, where user can define formulas, for data filtering for example. When I evaluate such formula against SQL database storage I translate them into SQL where clause for performance benefit (rather then filtering a java collection after reading everything to it). And in that case I have to do a special data type checking to avoid exceptions in order to achieve the same result as evaluating my formula against normal Java collections. I will have to dig deep to find out all the conversion rules, to protect myself against this kind of exceptions, which would be plain and easy with "no error" policy. I suppose generating SQL is not so much of a corner case nowadays. So maybe this is worth considering. Regards, Jacek --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
