#29590: Make defaults a required argument for QuerySet.get_or_create() and
update_or_create()
-------------------------------------+-------------------------------------
Reporter: Álex Córcoles | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: 2.0
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: new => closed
* resolution: => wontfix
* type: New feature => Cleanup/optimization
Comment:
I doubt there would be consensus for this change (I don't think the
problem you described is a common mistake and worth making the entire
Django ecosystem add `defaults={}` as needed) but you could write to the
DevelopersMailingList to get other opinions.
--
Ticket URL: <https://code.djangoproject.com/ticket/29590#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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.d9d8f63567a6ee9f11330dd0b550cde6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
