We are using Eclipselink 2.6.0.RC1 with H2 1.4.180 and most of the SQL for a large application is being generated by Eclipselink and is working fine.
Starting with versions greater than 1.4.180 and I not exactly sure which, the SQL that Eclipselink is generating is being rejected by H2 as invalid SQL. Looking at the SQL that is failing indicates that Eclipselink is generating requests to convert a String to a Timestamp as follows: TS '2090-01-01 00:00:00.0' when I am using H2 version 1.4.186 queries using TS as the name of the Timestamp conversion function fail, but for the same query if the name of the Timestamp conversion function is changed to TIMESTAMP then the query executes successfully. >From everything I can determine this change is intentional and a breaking change. Releases from somewhere around1.4.180 and before do not support TIMESTAMP as the name of the String to Timestamp conversion function and releases somewhere after 1.4.180 do not support TS as the name of the String to Timestamp conversion function. So this looks like a breaking change, but your documentation hasn't announced that such a change has been made to the code base. 1) Have you changed the behavior of the code and introduced a non-backward compatible breaking change? 2) If the behavior has changed when will you document the behavior? -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
