The fix is in Version 1.3.174 (2013-10-19).
Is it possible to find out in which version the bug was introduced? I have deployments using 1.3.168 and i don't remember having seen this happening. I have seen it happening in 1.3.173 though. I'm wondering whether to upgrade the 1.3.168 deployments or leave them alone. -- 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.
