Hi, Thanks for your mail! This is a bug. The Recover tool doesn't correctly convert CLOB data with non-ASCII characters. For me, even setting file.encoding to UTF-8 doesn't work (not sure why yet). I will fix this.
A workaround is to convert the database using the SQL statements SCRIPT TO / RUNSCRIPT FROM or the tools Script / RunScript. Regards, Thomas On Fri, Feb 5, 2010 at 11:13 AM, Oliver Meincke <[email protected]> wrote: > Hi, > > first a big 'Thank you' for your great work, Thomas! We've been using > H2 for a long time now and never had any problems. > > But now we've encountered a problem when upgrading from 1.1.118 (old > file format) to 1.2.128 (page store). We're using hibernate and some > longer texts are stored in a lob. When the database is converted to > the new format, some characters (german umlaute for example) are not > converted correctly. A short example to reproduce the bug can be found > here: > > http://pastebin.com/m3527dd93 > > First, run the example using h2 1.1.118 and page_store=false. A string > is stored and retrieved from the database. > Now run the program with h2 1.2.128 and page_store=true. The database > ist being converted and the string is stored in the database again. > But when the now two strings are read from the database, only the > second string is displayed correctly. > > Geetings and thanks in advance, > > Oliver > > -- > You received this message because you are subscribed to the Google Groups "H2 > Database" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/h2-database?hl=en. > > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
