fix: Fixed trasaction aborted issue in bulk operation #38
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Solved transaction aborted issue
issue=> 8848digital/erpnext#481
Desc
The error
psycopg2.errors.InFailedSqlTransactionwith the messagecurrent transaction is aborted, commands ignored until end of transaction blockusually indicates that an earlier SQL operation in the current transaction failed, which causes subsequent queries to be ignored because the transaction is already in a failed state.In PostgreSQL, when a transaction encounters an error, it is marked as "failed." Any further SQL operations within this transaction will be ignored until the transaction is rolled back. In the Frappe framework, if an exception occurs during a database operation and you do not explicitly handle it, the current transaction may remain in a failed state.