1 | | In non-autocommit mode, after an error has occurred (specifcally, IntegrityError and ValidationErrors are known to cause the issue, but I haven't fully investigated which errors can cause this), the db connection's needs_rollback attribute is set to True. When the flag is set to True, no further orm queries can be made to the database. Once this has happened, there appears to be no way to clean up the transaction, as a transaction.rollback() does not unset this flag. |
| 1 | In non-autocommit mode, after an error has occurred (specifcally, `IntegrityError` and `ValidationError` are known to cause the issue, but I haven't fully investigated which errors can cause this), the db connection's `needs_rollback` attribute is set to True. When the flag is set to `True`, no further ORM queries can be made to the database. Once this has happened, there appears to be no way to clean up the transaction, as a `transaction.rollback()` does not unset this flag. |