[h2] JdbcConnectionPool & Auto_Server argument

Hi, I use a connection pool to manage connections. The JdbcDataSource' url contains the argument "AUTO_SERVER=TRUE". Everything works well within my application. But when I use another client (SQL Workbench/J) to connect to the database, it throws the error stating the database is inaccessible

Re: [h2] Re: Connecting through the PG Server

On 2016-01-07 07:13 AM, Tim wrote: I have looked at the code and found the issue. I am using the PG Server for connectivity and it has the PostgreSQL mode hard coded which overrode the MODE I set when starting H2. I am logging into the PG Server with an admin user to generate the

Re: [h2] Corruption vs endless background compact process

Hi, For #1: this is a known problem which was fixed in later versions. See the change log, version 1.4.188 Beta (2015-08-01): "MVStore: power failure could corrupt the store, if writes were re-ordered." For #2: it should no longer be needed. I think later versions write less in the background

Re: [h2] To which H2 version should we update in productive environments

Am Montag, 7. Dezember 2015 12:46:12 UTC+1 schrieb Thomas Mueller: > > Hi, > > 1.4 is still beta because of the new MVStore storage engine. If you > disable that, then I consider it stable. Just append ";mv_store=false" to > the database URL. > > Regards, > Thomas > > On 8 January 2016 at 11:04,

[h2] Sponsorship/funding for issue #156 - Support getGeneratedKeys() for batches

Hi, I have just added a comment on #156 saying that I would like to try and organise sponsorship/funding for #156. I don't know what the correct way to go about this is so I'm looking for guidance on that. Someone can contact me directly via robin.bygave (at) gmail dot com if you wish to