#35466: Create new objects method get_or_none() to avoid boilerplate try/except
-------------------------------------+-------------------------------------
Reporter: Sebastian Muthwill | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: models, query, | Triage Stage:
queryset, get | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* resolution: => wontfix
* status: new => closed
Comment:
Please take a minute to
[https://code.djangoproject.com/query?description=~get_or_none&status=assigned&status=closed&status=new&order=id&desc=1
search the bug tracker] before requesting features
[https://docs.djangoproject.com/en/dev/internals/contributing/bugs-and-
features/#requesting-features as documented] and referenced in the
[https://code.djangoproject.com/newticket please read first section of the
ticket creation page]
Duplicate of #33384, #11352, #2659, all of which were wontfixed.
--
Ticket URL: <https://code.djangoproject.com/ticket/35466#comment:1>
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/0107018f886d976c-f7f65c4f-00d9-4d9b-8aac-a750e9b404d6-000000%40eu-central-1.amazonses.com.
