#34523: Model.objects.update_or_create method sometimes raises
TransactionManagementError
-------------------------------------+-------------------------------------
Reporter: gatello-s | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution:
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 Mariusz Felisiak):
Replying to [comment:13 Simon Charette]:
> As for the heuristics to determine if a backend supports transaction the
situation is definitely weird on MySQL as supports is on a per-table basis
and `default_storage_engine` is really just a guess at that. In this sense
331a460f8f2e4f447b68fba491464b68c9b21fd1 is backward incompatible as it
stopped using savepoints which could have an impact on setups that have
mixed storage engines. Not sure if this is a supported setup though.
Would you recommend reverting 331a460f8f2e4f447b68fba491464b68c9b21fd1? (I
fine with that)
--
Ticket URL: <https://code.djangoproject.com/ticket/34523#comment:14>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070187cc95e753-87de1e37-09b8-40e6-a627-af8b7ffdf156-000000%40eu-central-1.amazonses.com.
