Transaction is commited when it should not be in the case of multiple exceptions [JDBC95] #133
Comments
Modified by: Steffen Heil (sh-solutions)Attachment: TestCase.java [ 10221 ] |
|
Commented by: Roman Rokytskyy (rrokytskyy) Fixed in HEAD |
Modified by: Roman Rokytskyy (rrokytskyy)status: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: Jaybird 2.2 [ 10053 ] |
Modified by: Roman Rokytskyy (rrokytskyy)status: Resolved [ 5 ] => Closed [ 6 ] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: Steffen Heil (sh-solutions)
Assigned to: Roman Rokytskyy (rrokytskyy)
Attachments:
TestCase.java
I think I found a strange bug in JayBird or Firebird.
So this may be a firebird issue as well.
I open a connection in non-auto-commit mode. I delete all entries in a table
and insert some new entries. That fails (acutally a bug in my software).
However the database should NOT get corrupted, as the transaction is NEVER
commited.
That works as expected.
If I try again, it fails again (as expected).
However, this time the database IS CORRUPTED, as the transaction seems to
get partially commited.
That effect already destroyed 3 databases of mine.
However I could isolate to problem and build a test case, which shows the
behavior. I'll attach it.
Commits: 96a5332
The text was updated successfully, but these errors were encountered: