|
The current version of Hsqldb supports transactions
only in isolation mode READ_UNCOMMITTED. I discovered this when trying to
correct the problems brought on by updating to Java 1.6. I was trying to
eliminate any other problems that might be caused by poor application
programming. When queried, JDBC reported READ_COMMITTED mode as I had
set it when that was not actually true. As a result, I changed a lot of the
application to AUTO-COMMIT wherever it was practical. According to the
developers, the next revision will handle all transaction isolation properly
although it sounds like with some additional overhead. BTW, Hsqldb is now
handled by Sourceforge. That should be a good thing.
Bayless
|