We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
pgx closes transaction on error. Then the lib returns missing error of "commit unexpectedly resulted in rollback".
The text was updated successfully, but these errors were encountered:
I checked this behavior in #76 If I return trm.ErrSkip in transaction section transaction will be commited. Is this correct?
trm.ErrSkip
Sorry, something went wrong.
ErrSkip doesn't connect with ErrTxCommitRollback. ErrSkip allows to commit on an application error not a database.
I think, I can close this issue, because the pgx docs said: PostgreSQL accepts COMMIT on aborted transactions, but px is treated as ROLLBACK.
PostgreSQL accepts COMMIT on aborted transactions, but px is treated as ROLLBACK.
The libs cannot fix this behavior.
No branches or pull requests
pgx closes transaction on error.
Then the lib returns missing error of "commit unexpectedly resulted in rollback".
The text was updated successfully, but these errors were encountered: