Fix handling of PendingRollbackError when processing large datasets #307
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.
This exception is raised when the database disconnects mid-operation and has to be handled outside the ORM.
This change includes some changes to the DB engine init args which make getting bad/stale connections less likely. It also changes the main work loop to operate on batches of paths, using a fresh DB session for each and adds handling for the remainder of a batch should an exception occur somewhere in the middle of it. SQLAlchemy errors are handled specially, by propagating them up to where they can trigger a rollback and allow work to continue with a new DB session.
This updates the Python version requirement to 3.12 (to get itertools.batched())