#34523: update_or_create not work in parallel insertion
-------------------------------------+-------------------------------------
Reporter: gatello-s | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: update_or_create | Triage Stage:
TransactionManagementError | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
Backends that don't support transactions is not a particularly well tested
area of the code base. Do we even run the full test suite against MyISAM?
I'm curious as to whether you run into the same issue by making your
`TransactionManagementErrorTest` testcase extend `TransationTestCase`
instead of `TestCase`. I would expect `transaction.atomic` to be a noop
when the backend doesn't support transactions so I wouldn't be surprised
if there was an issue with nested `atomic` blocks on such backends as they
also don't support savepoints by definition (Remember that `TestCase`
wraps each tests in an outer `atomic` block).
--
Ticket URL: <https://code.djangoproject.com/ticket/34523#comment:8>
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/01070187c330f69f-158c0ed5-fd56-4125-bc31-b8ddc2b98d9e-000000%40eu-central-1.amazonses.com.
