[h2] H2 (embedded) uses a lot of memory for large Union Statement

Hi, H2 SQL statements containing a lof of UNION ALL expressions (top level) consume a lot of memory, especially when the unioned SELECT queries are quite large (like for generated statement that we use). According to JProfiler, this is caused because the H2 SelectUnion objects reference each

Re: [h2] Slow insert on index vs hsqldb

I don't think hsqldb supports on-disk indexes, it's indexes are always stored only in RAM, so it has less disk IO to perform. (but I could be wrong, corrections welcome). At the moment, H2 does not support memory-only indexes on disk-based data (but patches are welcome) -- You received this

[h2] Missing jar file in maven repository

Hi, I'm trying to use the h2 database within a gradle project. Unfortunately there is no jar file into the respective repo (http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22com.h2database%22). Has anybody a useful hint about this error? Thanks, Juergen -- You received this message because

Re: [h2] Missing jar file in maven repository

Le 22/05/2015 15:03, Eric Chatellier a écrit : search UI bug. Or invalid pom file : http://repo1.maven.org/maven2/com/h2database/h2/1.4.187/h2-1.4.187.pom -- Éric Chatellier - www.codelutin.com - 02.40.50.29.28 -- You received this message because you are subscribed to the Google Groups H2

Re: [h2] Missing jar file in maven repository

Le 22/05/2015 13:57, Jürgen Henning a écrit : Hi, I'm trying to use the h2 database within a gradle project. Unfortunately there is no jar file into the respective repo (http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22com.h2database%22). Has anybody a useful hint about this error? search

[h2] Erroraccessingdatabase

Hi, I'm new to H2, and I have to work with an pre-existing h2 database. So basically, when I first access the database through the console, I manage to log in. However, after disconnecting, and trying to re-access it, I get the following error: Unique index or primary key violation: PRIMARY

[h2] Unique index or primary key violation: PRIMARY KEY ON .PAGE_INDEX error

Hi, I'm new to H2, and I'm working with an already existing H2 database. When I first run H2 Console and access the database, I manage to get in. However, after I disconnect, and try to re-access the database, the following error occurs: Unique index or primary key violation: PRIMARY KEY ON

Re: [h2] Slow insert on index vs hsqldb

Hi, I think in this case, HSQLDB keeps the index on disk. I ran the test on my machine and it looks like there is a problem in H2 here when using the PageStore (which is the default for the version of H2 you are using). With a recent version of H2 (with the MVStore), it is much better, even

[h2] Congrats on MVStore!

Hey! I am the author of http://prevayler.org Some of you might know it. I am currently working on http://sneer.me , a P2P app platform. (Think Facebook, Twitter and Google but without a central server) I found within H2 a precious gem called MVStore :) It is perfect for my needs: embedding it