Re: [h2] Re: Can't get H2 1.4.193 in embedded mode to connect to existing ~/test.mv.db

that looks like you are using an old version of H2 in your application, which is opening a database based on the PageStore engine, hence the .h2.db file extension. the web console is running a newer version, and is defaulting to the MVStore engine, hence the .mv.db file extension ​ -- You receiv

[h2] Re: What will happen if......

Any other suggestions how curruptions like below could arise ? Caused by: org.h2.jdbc.JdbcSQLException: File corrupted while reading record: "22081 of 21060". Possible solution: use the recovery tool [90030-190] at org.h2.store.PageStore.readPage(Unknown Source) ~[h2-1.4.190.jar:1.4.190] at or

Re: [h2] Recovery DB Help

I'm afraid your database is corrupt, there is not really anything you can do. -- 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

Re: [h2] How to determine whether a file is H2 database?

Nope. -- 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 post to this group, send email to h2-database@googlegroups.com.

Re: [h2] What will happen if......

No. But if the primary application exits, the secondary application will lose it's connection to the database. -- 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 h

[h2] What will happen if......

We open our database with: Connection connection = new org.h2.Driver().connect(“jdbc:h2:file:\\Data;FILE_LOCK=FILE;AUTO_SERVER=TRUE;MODE=REGULAR;MV_STORE=FALSE;DB_CLOSE_DELAY=0", new Properties() ); We close our database with: connection.close(); What will happen if the user

[h2] Re: Entries in a table containing Geometries cannot be found when the Geometry is empty ( Row not found when trying to delete from index )

Update (just that this ) won't happen: The issue could be resolved, the pull request https://github.com/h2database/h2database/pull/391/

Re: [h2] Huge memory requirements for simple select order by - why?

I have implemented this for my special case and I keep having problems: I use a prepared select statement with an LIMIT ? OFFSET ? clause I retrieve just 10 of the 100 million rows every time. I initially still got out of memory exceptions and ended up giving 80G heap space to the process.