Re: [h2] H2 seems to create a huge number of orphan lobs since 1.4.183.

2015-03-25 Thread Thomas Mueller
Hi, (1) add a manual command to clean them up >> > Yes, that would be an option, and we would not have to change behavior by default (which is a risk as it could break existing applications). > (2) change it so that the client can only read from a BLOB while a >> transaction is open. Flush any t

[h2] Persistent to In-memory Database

2015-03-25 Thread Thomas Mueller
Hi, See the documentation at http://h2database.com/html/grammar.html#create_table Regards, Thomas On Tue, Mar 24, 2015 at 5:24 PM, Jason > wrote: > Not a problem... I rebuilt my database using *MEMORY* on each table. > > What is the difference between mem in the url and MEMORY on the tables? >

Re: [h2] H2 seems to create a huge number of orphan lobs since 1.4.183.

2015-03-25 Thread Kenton Garner
Noel - I would be in favor of either of those two options. #2 seems reasonable to me, but I understand you may have an historical precedent. On Wednesday, March 25, 2015 at 3:13:20 AM UTC-4, Noel Grandin wrote: > > > > On 2015-03-23 10:43 AM, Thomas Mueller wrote: > > > > This is a problem, an

Re: [h2] Data corruption from repeatedly closing DB and re-opening it immediately

2015-03-25 Thread Joonas Pulakka
Great! Keep up good work! Best, Joonas keskiviikko 25. maaliskuuta 2015 8.47.27 UTC+2 Thomas Mueller kirjoitti: > > Hi, > > Thanks a lot for the great test case! This is a bug that was introduced in > the last version, in a mechanism to remove unreferenced CLOB and BLOB > blocks. This mechanism

Re: [h2] H2 seems to create a huge number of orphan lobs since 1.4.183.

2015-03-25 Thread Noel Grandin
On 2015-03-23 10:43 AM, Thomas Mueller wrote: This is a problem, and I don't have a good solution for that I'm afraid. Closing the database or closing the connection from time to time are not good solutions I think. I can think of a few options (1) add a manual command to clean them up (