Re: [h2] Recovery tool does not handle LOBs correctly (explanation and fix is proposed)

Hi Thomas, Sorry to bother, do you have any update on this? On Saturday, August 5, 2017 at 12:23:58 AM UTC-5, Sai K wrote: > > Hi Thomas, > > Iam running into similar issue > > https://stackoverflow.com/questions/45518411/h2-database-error-while-trying-to-use-runscript > Iam trying to recover

Re: [h2] Recovery tool does not handle LOBs correctly (explanation and fix is proposed)

Hi Thomas, Iam running into similar issue https://stackoverflow.com/questions/45518411/h2-database-error-while-trying-to-use-runscript Iam trying to recover using 1.4.196 but still getting same error? Is this issue resolved in the latest version? Thanks, Sai On Sunday, February 12, 2017 at

Re: [h2] Recovery tool does not handle LOBs correctly (explanation and fix is proposed)

Hi, I agree, but releasing H2 will take a few weeks I'm afraid. Regards, Thomas On Thu, Feb 2, 2017 at 12:25 PM, LRichard wrote: > Hi, > > It would be great if version 1.4.194 could be released in order to > integrate the patch. > (We have corrupted customer databases

Re: [h2] Recovery tool does not handle LOBs correctly (explanation and fix is proposed)

Hi, It would be great if version 1.4.194 could be released in order to integrate the patch. (We have corrupted customer databases and cannot use the latest official h2 jar to recover these databases) Thanks -- You received this message because you are subscribed to the Google Groups "H2

Re: [h2] Recovery tool does not handle LOBs correctly (explanation and fix is proposed)

Finally, PULL request was created at github. On Wednesday, July 20, 2016 at 8:49:29 AM UTC+3, Thomas Mueller Graf wrote: > > Hi, > > It would be better if the recovery mechanism does not use an internal > mechanism of H2 (not use the "hidden" INFORMATION_SCHEMA.LOBS tables, and > instead

Re: [h2] Recovery tool does not handle LOBs correctly (explanation and fix is proposed)

Hi, It would be better if the recovery mechanism does not use an internal mechanism of H2 (not use the "hidden" INFORMATION_SCHEMA.LOBS tables, and instead use "real" tables). This is fixed in the MVStore case, where "real" tables are used (actually just INFORMATION_SCHEMA.LOB_BLOCKS). So there

[h2] Recovery tool does not handle LOBs correctly (explanation and fix is proposed)

Hi. Recently I have observed that recovery tool strangely breaks LOBs (in particular CLOB objects in my case, but same is applicable to BLOB). After recovery CLOB values are not what they were in original H2 file before recovery process is run. More than a day of debugging and some