Hi, I have some news on this. The main problem is a bug in the b-tree index code that speeds up updates. There is a 'kill switch' for this feature, you can disable it if you append ";optimize_update=false" to the database URL. The test does no longer fail if I did this. There is another problem I want to solve as well: when running this test case, the b-tree pages are split at the wrong position, so that the database is much larger than needed.
Both problems only occur when using an index on variable size data, if the data to be indexed is very big (larger than 1 KB). I will fix both problems this weekend and will release a new version. But first I want to create a better test case to make sure this will not break in the future. Regards, Thomas On Fri, Apr 6, 2012 at 9:51 AM, Thomas Mueller <[email protected]> wrote: > Hi, > >> This bug is a bit scary as I also have indices on not-so-small varchar >> columns. > > Yes, it is scary. > >> Thomas, can we know when do you plan to release the next H2 version? > > As soon as this bug is fixed, I hope this weekend. > > Regards, > Thomas -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
