I am using MySQL mode indeed because the app sends statements like in https://github.com/h2database/h2database/pull/1287, which was only fixed/allowed in MySQL mode. Granted the latter is not supported in Oracle but "the app" looks up the DatabaseMetadata to use the right syntax.
The errors on DELETE are not blocking ones in the app so we can deal with it outside of the app, however I am wondering why so many features are restricted to one or some modes. What's the harm ? Maybe we should have a STRICT_COMPATIBILITY setting to enforce or not. On Saturday, April 27, 2019 at 5:04:27 PM UTC-4, Yan wrote: > > I have a 3rd-party application that supports Oracle and I wanted to test > it with h2. > It errors out on DELETE <table> WHERE ... because H2 requires the FROM > keyword. Weird construction as I didn't know but Oracle, MSSQL and maybe > others have the FROM as optional. > > Hence the request to make it optional in H2 too, regardless of the > compatibility mode. > -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
