Hi, Thanks for the test case! I could reproduce the problem. It occurs when the cache size is smaller than the transaction, which is the case in the test case you sent. H2 doesn't support very large transactions that well currently, one of the top feature requests on the roadmap is "Support large inserts and updates". I'm not sure however when I will have time to implement it (it will probably be only available when using the the page store, version 1.2.x).
As a workaround, I suggest to split large transactions into smaller ones, or use a larger cache size. I create a new issue http://code.google.com/p/h2database/issues/detail?id=157 with a simpler test case. 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.
