Every time I post about a bug in H2, somebody is trying to convince me that there is no bug and that I'm doing something wrong. Nice to see this time is no different. This backward compatibility is important to me ;)
>From user-code perspective there is no difference between "COMMIT" and "COMMIT TRANSACTION txnName" in a non-crashed connection. The latter form is necessary during post-crash recovery as you might encounter more than one in-doubt transactions and have to resolve them one by one. At least that's how it's documented ( http://www.h2database.com/html/advanced.html#two_phase_commit) and that's the way it has worked for years with PageStore. I see no reason why it should be any different with MVStore, esp. considering the fact that I've been previously told by H2 devs that "Backwards compatibility is important to us". Jokes aside, the bug does not vanish just by using "COMMIT TRANSACTION txnName" instead of "COMMIT". With MVStore, in case of crash during an open transaction, the last resolved in-doubt transaction appears INFORMATION_SCHEMA.IN_DOUBT. This doesn't happen with PageStore. -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
