As the subject says, I'm doing a SELECT.. FOR UPDATE to lock a row. Sometimes this is followed by an UPDATE, sometimes not. In the case of an UPDATE, I commit() the connection which releases the lock. All fine.
When not updating the row contents, I close() the connection. This however seems to leave the row lock around. I can, also in this case, call either commit() or rollback() before the close(), then the lock is released. But why would I be required to do this? Closing a connection (whether voluntarily or due to a networking issue) should cleanup its resources as well (e.g. locks). - Martin -- 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.
