[h2] Re: Query Optimizer limitations

Also, if you can, try loading the data into another DB and running the same querry. This will give you an idea if it is a problem with how you are using H2, or if it is just a hard query for most engines to optimize. Also, you may get faster results if you use the H2 PageStore engine. On

[h2] Re: Query Optimizer limitations

As far as I am aware, the problem with the query optimizer is that it does not use indexs in every situation that one might expect. But yours seems to be using the index. So, I don't know what else it could be (but I am no expert at H2). How long does it take to run the query? How many rows

Re: [h2] Re: File corruption with nioMemLZF

Can you post your performance test code? On Thu, 19 Jan 2017 at 18:36, Anatolii K wrote: > Sorry to say so, but performance dropped dramatically. > Previously compressed storage was just a bit slower than uncompressed. > But now it become almost 100 times slower! > > > > On

Re: [h2] Re: Voting up for SQL Trigger

No, I meant that I'd be happy to accept a patch that implemented such a thing, not that I intended to do it myself On Thu, 19 Jan 2017 at 16:35, Yan wrote: > Thanks Noel - any target release and ETA for it ? > > > On Wednesday, January 18, 2017 at 11:29:38 PM UTC-5,

Re: [h2] Re: File corruption with nioMemLZF

Sorry to say so, but performance dropped dramatically. Previously compressed storage was just a bit slower than uncompressed. But now it become almost 100 times slower! On Thursday, January 19, 2017 at 1:32:49 PM UTC, Noel Grandin wrote: > > I have pushed a fix for this, it now survives your

Re: [h2] Re: Voting up for SQL Trigger

Thanks Noel - any target release and ETA for it ? On Wednesday, January 18, 2017 at 11:29:38 PM UTC-5, Noel Grandin wrote: > > I'd be happy with a patch that did that > On Tue, 17 Jan 2017 at 22:47, Yan > wrote: > >> Fair enough Noel. >> >> What about opening up inline

Re: [h2] Last chance SQL editing in JDBC + fooling DBProduct name

Thanks Kerry. It turns out there are many "driver delegaters" out there. One I find interesting is: http://www.nic.uoregon.edu/~amorris/regression/testtau/tau2/tools/src/perfdmf/src/database/DBConnector.java It's not designed for H2 backend but highlights the transformation you can do in a

Re: [h2] Re: File corruption with nioMemLZF

I have pushed a fix for this, it now survives your test. I had to simplify the current code and just synchronize the methods, which means it may lose some performance. If this is a problem for you, I'm sorry, but you'll have to come up with some patches yourself. -- You received this message

[h2] Re: File corruption with nioMemLZF

Sorry for bothering you, but could you please look at it -- 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

[h2] Re: Query Optimizer limitations

Hi Adam, I mean query is very slow. Explain plan looks good and it is using index. I did not compare with other databases. Thanks. -- 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