Thank you fro replying, and it does work that your suggestion on using non_keywords settings, this helps because I don't have to surround backticks for keywords like "key" and "value".
While, I was not trying to look for a bug-for-bug compatibility, I have encountered some cases that worked on 1.4.200 either MySql or Oracle mode, but not worked on 2.0.206 under a specific mode. For example, under 1.4.200 either Oracle or Mysql , I can use "create table users( id int(10) not null primary key auto_increment, name varchar(30 byte) default null, password varchar(30) default null, value varchar(30) default null, date date(8) default null );" Under 2.0.206, for oracle mode int(10) needs to be int; auto_increment is no longer supported; date(8) needs to be date for mysql mode int(10) still works; auto_increment is supported; date(8) needs to be date; varchar(30 byte) needs to be varchar/varchar(30) And these cases are not bugs, but compatibilities under different modes; Is there any mean like "runscript" to get rid of these incompatibilities? Thank you again. Best regards, Yuqiang 在2022年1月7日星期五 UTC+8 15:04:51<Evgenij Ryazanov> 写道： > Hello. > > FROM_1X flag of RUNSCRIPT command allows keywords to be used as > identifiers only in the imported script. This option doesn't change > behavior of database after data import. > > If your application tries to misuse VALUE as unquoted identifier it needs > to be fixed anyway, you need to quote it as "VALUE". If you cannot fix > your application right now, you can add ;NON_KEYWORDS=VALUE to JDBC URL > of H2. > > Please also note that H2 2.0 is very different from H2 1.* and doesn't > provide bug-for-bug compatibility. > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/4f8aa823-021d-436e-80ba-5dbcec728898n%40googlegroups.com.
