Last year we decided to upgrade a program of ours to what was then the
latest version of H2, but with one thing and another it took a
ridiculous amount of time to get around to the update (hence the fact
that we've just updated to a relatively old version.

Of course it all went perfectly well on our tests, but having gone
live we started to get problem reports concerning the synchronization
of local H2 database tables with our central servers. After
considerable investigation I concluded at least one problem
manfestation was probably down to

>Queries that are ordered by an indexed column returned no rows in certain cases
>   (if all rows were deleted from the table previously, and there is a low 
> number of rows
>    in the table, and when not using other conditions, and when using the 
> default b tree index).

Fixed in 111

But with another problem I found that I was not getting a full
resultset on a simple table with three integer key fields when I
specified the first two in the WHERE clause. The missing records could
be selected if all three keys were specified. Presumably an error in
the index range scan. This problem went away if I dropped and rebuilt
the primary key index (or deleted the index file), but it came back
next time I synchronized the table.

(Because we're merging part of the local table with part of the
central table if a record goes missing from the SELECT the code
usually tries to insert it from the central data, which will cause a
uniqueness violation).

For a couple of users I've switched to version 1.1.119 (I don't want
to rebuild the databases for the lastest version, and I figured the
last of the 1.1 releases would be a point of maximum stability).
rebuilt the indices and everything seems fine.

What I'm looking for is confirmation that the b-tree problem which
caused the officially fixed bug could reasonably manifest in the range
scan context, so I can be reassured that this problem is very likely
to be fixed.

-- 
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.

Reply via email to