Hi, >> > 1) unclear why to convert 'a' to int rather then 1 to varchar
I don't know exactly, but that's how PostgreSQL works, and PostgreSQL is usually right :-) I'm almost sure the conversion order is defined in the SQL standard (but I don't know where). But existing databases don't always follow the standard as we see... > Well, the exception is thrown because 'a' cannot be converted to 1, > not because it's unclear. If it was for ambiguity reason it should > read something like "Incompatible data types in expression: 1='a' " > and it should have been thrown also for 1='1'. select * from test where '1'=1 This works for PostgreSQL, HSQLDB, and H2. But it does not work for Derby. > 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. 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 -~----------~----~----~----~------~----~------~--~---
