#22540: .save() called in multiple "creation" queryset functions
-------------------------------------+-------------------------------------
Reporter: craig.labenz@… | Owner: nobody
Type: | Status: closed
Cleanup/optimization | Version: master
Component: Database layer | Resolution: fixed
(models, ORM) | Triage Stage: Ready for
Severity: Normal | checkin
Keywords: creation | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by Claude Paroz <claude@…>):
In [changeset:"faa8c71fd9e97794e73f7e7564446846d72d8bb2"]:
{{{
#!CommitTicketReference repository=""
revision="faa8c71fd9e97794e73f7e7564446846d72d8bb2"
Moved misplaced transaction.atomic from 0dce44e16b
Thanks Florian Apolloner for noticing the issue and Aymeric
Augustin for the expertise.
Refs #22540.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/22540#comment:5>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/080.581bfeeb3bff1f03e0875b74bcc80430%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
