#34884: Half bug/half enhancement : inconsistent behavior of get_or_create()
regarding related attributes cache
-------------------------------------+-------------------------------------
Reporter: Laurent Lyaudet | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: ORM get_or_create | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham):
I have said my piece. I don't think the additional complexity in Django is
warranted for what looks like a niche case. The workaround of setting the
attribute after `get_or_create()` isn't particularly burdensome. You can
try to solicit the opinions of others if you are so motivated.
--
Ticket URL: <https://code.djangoproject.com/ticket/34884#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018bdab98b56-f4a2b23b-ff8e-4a6b-9940-3ac0b1f4d1a2-000000%40eu-central-1.amazonses.com.
