New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrity violation exceptions are being hidden for EXASOL. #1558

Open
wants to merge 1 commit into
base: master
from

Conversation

Projects
None yet
2 participants
@YLesko

YLesko commented Oct 12, 2017

I have discovered that when java.sql.Connection#setAutoCommit set to 'false' PK/FK violations ignored. After debugging I noticed that Exasol does these checks on java.sql.Statement#close rather than on java.sql.PreparedStatement#executeUpdate. Checked JdbcUtils class I found that it is ignoring all "on close" exceptions however this specific case should be handled because otherwise transactions management won't work with EXASOL.

@pivotal-issuemaster

This comment has been minimized.

Show comment
Hide comment
@pivotal-issuemaster

pivotal-issuemaster Oct 12, 2017

@YLesko Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

pivotal-issuemaster commented Oct 12, 2017

@YLesko Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

@pivotal-issuemaster

This comment has been minimized.

Show comment
Hide comment
@pivotal-issuemaster

pivotal-issuemaster commented Oct 12, 2017

@YLesko Thank you for signing the Contributor License Agreement!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment