[h2] Re: 1.3.172 vs 1.4.199

Thank you so much. It's working now. I think I need the 1.4.199 version because in my user program h2 I have several threads that concurently access the database to modify it. Le mercredi 17 juillet 2019 13:38:29 UTC+2, Patrice a écrit : > > I have a database managed under h2 1.3.172. I wanted

[h2] the database grows

In a database managed via H2 (version 1.4.199), any request of the type "select" seems to increase the size of the base (8 KO each time) which I can possibly understand to keep a trace of the transactions. Is there a way however to return to the original size if we did not change anything in

[h2] Re: the database grows

Maybe your SELECT statement returns some LOBs or it has FOR UPDATE clause? Otherwise it should not affect the size of database in any way. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails

[h2] Re: the database grows

My request does not return "LOBs" and does not include an "UPDATE". However, I can't reproduce the problem so I consider it solved. Le mercredi 17 juillet 2019 15:51:36 UTC+2, Evgenij Ryazanov a écrit : > > Maybe your SELECT statement returns some LOBs or it has FOR UPDATE clause? > Otherwise

Re: [h2] Re: Corrupt Database Chunk Wont Recover

107 is on the download page. That one should work also. I still have 196 from before. Perhaps the H2 guys can help you with that. -- 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,

Re: [h2] Re: Corrupt Database Chunk Wont Recover

197... -- 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-database+unsubscr...@googlegroups.com. To view this discussion on the web visit

[h2] Memory increase after Update from 1.2 to 1.4.199

Hi, we use the H2 Database in our software as embedded solution. After the update from 1.2 to 1.4.199, the memory is increasing to factor ~2. In numbers: from HeapSpace use ~7,9GB to ~14,9GB. I have searched in this forum and with google, but i don't found any solution for our problem here.

[h2] Re: 1.3.172 vs 1.4.199

Hello. Your version is very old. Automatic upgrade is not always clean. You need to export your database to SQL with a SCRIPT TO 'filename.sql' command using 1.3.172. After in you can create a new database with 1.4.199 and execute RUNSCRIPT FROM 'filename.sql' to populate it with your data.

Re: [h2] Re: 1.3.172 vs 1.4.199

Thank you so much. It's working now. I think I need the 1.4.199 version because in my user program h2 I have several threads that concurently access the database to modify it. Le mer. 17 juil. 2019 à 15:03, Evgenij Ryazanov a écrit : > Hello. > > Your version is very old. Automatic upgrade is

[h2] 1.3.172 vs 1.4.199

I have a database managed under h2 1.3.172. I wanted to update with version 1.4.199. I make a simple SELECT on a table, I disconnect and when reconnecting I get the following error: *Single index violation or primary key: "PRIMARY KEY ON" "" ".PAGE_INDEX"* *Unique index or primary key violation: