We are doing integration testing using HSQLDB, we still do full blown integration test with oracle, but on developers PC's Oracle XE is way too heavy, so we have a local build which uses HSQLDB. This does do stuff that requires reasonable concurrency from the DB and tends to cause timeouts otherwise.
We always suffered either from timeouts or when we went to MVCC, the missing lobs issue. On Thursday, May 30, 2013 7:40:57 PM UTC+10, Noel Grandin wrote: > > > On 2013-05-30 10:56, jason...@gmail.com <javascript:> wrote: > > The real issue is by default h2 locks entire table so only one thread > > can perform dml stuff this makes it unsuitable for our situation. And > > we actually only use h2 in test we use Oracle or sql server in > production > > H2 is pretty fast, even with it's simple locking strategy. > What are you doing that requires so much speed that single-threaded > access to a table is insufficient? > Especially since you're only using it in test. > -- 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. Visit this group at http://groups.google.com/group/h2-database?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
