I have no idea what the underlying problem is. But if you could create a standalone test case for it I could probably track it down.
In the meantime you could probably work around it by bumping up your cache size. Append something like this to your URL ;CACHE_SIZE=1024 where the size is in kilobytes. On 2014-05-21 10:42, [email protected] wrote:
one of our customers is facing the following problem while using our product, which uses an embedded H2 database (v. 1.3.173).
-- 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. For more options, visit https://groups.google.com/d/optout.
