[h2] Re: Corrupted database - new scenario

2019-06-18 Thread Silvio
Thanks Evgenij, that also makes sense. The database was indeed created using an older version of H2. -- 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] Re: Corrupted database - new scenario

2019-06-17 Thread Evgenij Ryazanov
Unfortunately, this tool exports medatadata (that may contain unquoted identifiers) as is. Databases that were created by 1.4.199 should not be affected. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop

[h2] Re: Corrupted database - new scenario

2019-06-17 Thread Silvio
Thanks Evgenij, That sounds plausible. It is just that I would have expected the Recover tool to be updated as well. Now the Recovery tool in 199 generates SQL that 199 can not process. A minor detail but that threw me off a bit. Fortunately I was able to recover the database so little harm

[h2] Re: Corrupted database - new scenario

2019-06-14 Thread Evgenij Ryazanov
Unfortunately, you need to enclose the "TABLE" into parentheses here with a some text editor. It is a new keyword. Recent versions of H2 can load old databases with such unquoted identifiers, but they can't load a script that contains them. Recent versions also always quote all identifiers