Well, that unfortunately does not solve the issue. After pulling out the UUID prefix for UUID-literals (did the same for the TIMESTAMP prefix) the generated SQL contains the following fragment:
U&'Co-effici\00ebnt' which looks like an obscure escape syntax for an extended character. Trying to import this with H2-1.4.200 fails. But since I use SCRIPT TO 'xxx' CHARSET 'UTF-8' I would expect no such escaping to be present in the file. Is there anything I can do to get rid of these escapes? On Thursday, 20 January 2022 at 10:52:15 UTC+1 Silvio wrote: > Thank you. I already expected that. I did not seek full backward > compatibility but since we use the database as a very plain table storage > without foreign keys, complex joins etc we can live with compatibility for > basic CREATE TABLE and INSERT statements only. So far we never had version > differences manifest themselves in the SQL and I was hoping there was some > kind of workaround. > > > On Thursday, 20 January 2022 at 06:14:42 UTC+1 Evgenij Ryazanov wrote: > >> Hello! >> >> H2 doesn't support and never supported downgrades. The oldest version >> that can open database files or SQL scripts from 2.1.210 is H2 2.0.202. >> >> You need to edit the exported SQL by yourself. For example, you can use a >> stream editor: >> >> sed "s/UUID '/'/" source.sql > target.sql >> >> But due to huge number of differences you may need to also edit many >> other declarations. >> > -- 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 h2-database+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/2ca36dcb-95af-4b61-837a-3e538391e8f2n%40googlegroups.com.
