[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

[h2] Corrupted database - new scenario

2019-06-14 Thread Silvio
I have another database corruption case. But this time it is on a PageStore DB and the exception contained a different message: Row not found when trying to delete from index ".I18: ( /* key:9812 */ 'ea5d1a40-2af9-4d88-8694-bac2c989f28d', '83e2f118-2201-475d-9746-a60a97155cb7', 4, 4,

[h2] Re: generated keys are "cleared" inside of Session during INSERT (to the table with AUTOINCREMENT column) when there is a trigger (Java code, obviously) that does another INSERT (to different tab

2019-06-14 Thread Vitali
I was working with codebase of few months old where described issue was faced. As we are maintaining some large projects with H2 as spatial embedded database , we build customized releases from source code from time to time. I took latest codebase and tested in the morning. I should