Changes between Initial Version and Version 1 of Ticket #27504


Ignore:
Timestamp:
Nov 21, 2016, 6:51:08 AM (8 years ago)
Author:
Tim Graham
Comment:

PR

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #27504

    • Property Triage Stage UnreviewedReady for checkin
    • Property Type UncategorizedBug
  • Ticket #27504 – Description

    initial v1  
    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.
     1In 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.
    22
    33An example failing scenario:
     
    1515}}}
    1616
    17 This ticket is related to https://code.djangoproject.com/ticket/26340 and solves a subset of the scenarios affected by it.
     17This ticket is related to #26340 and solves a subset of the scenarios affected by it.
Back to Top