[h2] When to use MV_STORE=FALSE?

Hi all, I read about MVStore on the website, but are there any specific advantages compared to the old storage when using H2 as a pure JDBC database? I use version 1.4.188 and I'm wondering whether or not I should use MV_STORE=FALSE. The database contains several million rows and I use it in e

[h2] DEFRAG SHUTDOWN not removing lock?

Hi all, I use H2 version 1.4.188 in embeddded mode (mvstore enabled) and when I execute the statement DEFRAG SHUTDOWN I'm not able to open a new connection anymore. I use a single connection in my application and that gets closed when I execute the shutdown statement. (connection.isClosed() ret

[h2] sourceforge has probably still not fully recovered

The problem is most likely sourceforge; they had serious outages recently. The running joke is they were down for a week but hardly anyone noticed :) Cedric Buest blogged recently about uploading to maven central and bintray here: http://beust.com/weblog/2015/07/13/the-long-and-arduous-road-to-j

[h2] INIT in memory jdbc url

Hi, Why does the second connection calls the *INIT* when the database *tes*t is already in memory via the first connection? DriverManager.getConnection("jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;INIT=runscript from 'test/snapshot.sql'"); DriverManager.getConnection("jdbc:h2:mem:test;DB_CLO

Re: [h2] QUERY_CACHE_SIZE default value too low?

The thing is, I don't think there is a problem. I think that your code is not caching PreparedStatement 's properly, and the rest of H2 is so fast, that the only thing left in the profile is the parser initialisation :) On Wed, 05 Aug 2015 at 16:27, Steve McLeod wrote: > Hi Noel, > > I've actual

Re: [h2] MVStore with MVCC performance degradation

I had emailed you the trace file, but haven't got a reply, so here it is on Google drive shared to you: https://drive.google.com/open?id=0B7fRq__lUQbCRXJIM2NCVVdpZGM On Thursday, July 30, 2015 at 6:21:12 AM UTC-7, Noel Grandin wrote: > > > > On 2015-07-28 06:10 PM, Wes Clark wrote: > > Link to

Re: [h2] Database created with H2 1.3 possibly incompatible with H2 1.4 due to h2.storeLocalTime?

Hi, Steve, thanks a lot for your help! Regards, Thomas On Wednesday, August 5, 2015, Thomas Mueller wrote: > Hi, > > I can reproduce the problem now, and I think I know what the problem is. I > hope to have a fix ready in a few days. > > Regards, > Thomas > > > On Wednesday, August 5, 2015, S

Re: [h2] Database created with H2 1.3 possibly incompatible with H2 1.4 due to h2.storeLocalTime?

Hi, I can reproduce the problem now, and I think I know what the problem is. I hope to have a fix ready in a few days. Regards, Thomas On Wednesday, August 5, 2015, Steve McLeod wrote: > Here's a stack trace in the same scenario from h2 1.4.188 > > org.h2.jdbc.JdbcSQLException: General error:

Re: [h2] QUERY_CACHE_SIZE default value too low?

Hi Noel, I've actually solved this problem of PreparedStatement caching for my app by increasing QUERY_CACHE_SIZE to 100. But I'm interested in helping solve the bigger issue of why it seems to take a comparatively significant time to create a PreparedStatement. Cheers, Steve On Wednesday,

Re: [h2] QUERY_CACHE_SIZE default value too low?

Thanks, I'll have a look tomorrow at them in detail. Tell me, how often is JdbcConnection@preparedStatement called compared to how many times you execute a query? If it's every time, it means that your PreparedStatement caching is not working, which would indicate a problem with your connecti

Re: [h2] QUERY_CACHE_SIZE default value too low?

Noel, I've sent a comprehensive list of queries to you privately. The three most-executed queries are: select lastseen from player where playerid=? insert into TournamentPlayerHand (gameid, playerid, playername, seatnumber, stakelevelid, positionid, tournamentid, buyin, entries, casinoid, game

Re: [h2] QUERY_CACHE_SIZE default value too low?

Is it possible you could share a couple of the queries that are taking this long? Perhaps privately with Thomas and myself? On 2015-08-05 02:34 PM, Steve McLeod wrote: I've attached some screenshots from Java VisualVM CPU sampling. -- You received this message because you are subscribed to t

Re: [h2] Database created with H2 1.3 possibly incompatible with H2 1.4 due to h2.storeLocalTime?

Here's a stack trace in the same scenario from h2 1.4.188 org.h2.jdbc.JdbcSQLException: General error: "java.lang.ArrayIndexOutOfBoundsException: 4096"; SQL statement: ROLLBACK [5-188] at org.h2.message.DbException.getJdbcSQLException(DbException.java:345) at org.h2.message.DbException.get(D

Re: [h2] Database created with H2 1.3 possibly incompatible with H2 1.4 due to h2.storeLocalTime?

More info: I've been unable to reproduce this using the MVStore. I can make this problem happen when I only use h2 1.3.176 and I can make it happen when I only use h2 1.4.188. I initially create the database and load some data with h2.storeLocalTime=false, then restart the app with h2.storeLoc

Re: [h2] Database created with H2 1.3 possibly incompatible with H2 1.4 due to h2.storeLocalTime?

My latest findings: I can reproduce (again, sporadically) the problem by exclusively using h2 1.4.188 as follows: 1) set System.setProperty("h2.storeLocalTime", "false"), start the app, import some data; then 2) restart the app with System.setProperty("h2.storeLocalTime", "true") and import som

Re: [h2] Using H2 as an embedded database for CAD/GIS software

Hello, Steve Hruda was working on an interface with JTS as default implementation : https://github.com/shruda/H2-Mirror/tree/AbstractValueGeometry You have API here https://github.com/shruda/H2-Mirror/blob/AbstractValueGeometry/h2/src/main/org/h2/api/IValueGeometryFactory.java I don't know if th