Hello all, Executing SCRIPT TO command from H2 2.1.210 generates an SQL file that can not be processed by an application using 1.4.200. The culprit seems to be that in INSERT statements UUID values are exported in their hex-string format prefix by the UUID keyword. So it looks like
UUID 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' instead of plain 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' which breaks 1.4.200. Although most of our conversions are going the other way (which does work) we can currently not prevent having to move a database from a server running 210 to one that still runs 200. Is there a flag or something that can make 210 generate the legacy syntax? -- 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/e97ad691-660e-4694-b825-649b3707ddbbn%40googlegroups.com.
