Fixing the H2 source is easier said than done, changing to HSQLDB was actually a few hours of work, granted they were a painful few hours, but when you use JPA and Hibernate, switching DB's is relatively painless.
We are still using H2 for a lot of stuff, even in production, we just use HSQLDB to replace Oracle in test and dev as it behaves concurrently much better. We use H2 as a configuration store for lots of stuff that would be overkill to use with Oracle. The row level locking is what we really needed and thus because MVCC is experimental with H2, we had to go with another DB where the MVCC support works well with CLOB. I would love to go back to H2 for everything and will certainly keep an eye on MVSTORE. I do contribute to open source myself - being a committer on Apache CXF, but hacking on H2 to fix this particular issue is way beyond my capability especially considering what little time I have. On Thursday, May 30, 2013 4:48:31 PM UTC+10, Kartweel wrote: > > I'm using MVCC and the only problems I've come across appear to be with > LOBS (that's ok for me, don't really need them for my use case). > > What I mean is that it may have been less work for you to try and fix > the H2 source (Seeing the issues seem to all be with LOBS) rather than > change to hsqldb (And there would have been other people benefit from > that also). Isn't that meant to be one of the good things about open > source? > > I know, I get it from my programmers all the time (They say there is an > issue with the library, so they make their own or work around it, which > usually doesn't work very well anyway), I tell them to fix it upstream! > that is the whole point! > > And it is getting lots of attention, the entire file store is being > re-written to accommodate for MVCC right from the start!, that is why > they haven't been giving attention to maintaining the current > experimental MVCC mode (Please correct me if I am wrong) > > > > On 30/05/2013 2:30 PM, Noel Grandin wrote: > > > > On 2013-05-30 00:34, Jason Pell wrote: > >> We finally got sick of this issue and migrated to HSQLDB for MVCC and > >> no more missing lob issues. We still use H2, but only for storing > >> configuration stuff that does not need to be updated concurrently. > >> It's a shame more attention has not been shown to this issue, because > >> it was certainly frustrating having to change over to HSQLDB. > > > > It's an open-source project, so I guess the problem would be yours for > > failing to provide a fix. > > > > (Nobody on this project, to my knowledge, is being paid to work on it). > > > > Now, if you want to provide a test-case for your non-MVCC table lock > > timeout problem, I could maybe help you there, but the MVCC code is > > still experimental, so I'm not touching that, especially since we're > > going to drop it when Thomas' new MVStore engine reaches maturity. > > > > > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
