#26552: `TransactionTestCase.serialized_rollback` fails to restore objects due
to
ordering constraints
-------------------------------------+-------------------------------------
Reporter: Aymeric Augustin | Owner: Matthijs
| Kooijman
Type: Bug | Status: closed
Component: Testing framework | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"98f23a8af0be7e87535426c5c83058e2682bfdf8" 98f23a8]:
{{{
#!CommitTicketReference repository=""
revision="98f23a8af0be7e87535426c5c83058e2682bfdf8"
Fixed #26552 -- Deferred constraint checks when reloading the database
with data for tests.
deserialize_db_from_string() loads the full serialized database
contents, which might contain forward references and cycles. That
caused IntegrityError because constraints were checked immediately.
Now, it loads data in a transaction with constraint checks deferred
until the end of the transaction.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26552#comment:10>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.59f127714dbd552bce219dcde5d3e992%40djangoproject.com.
