#35014: update_or_create using update_fields opt out
-------------------------------------+-------------------------------------
Reporter: Jordan Hyatt | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: 4.2
(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 Mariusz Felisiak):
* status: new => closed
* resolution: => wontfix
Comment:
I appreciate you'd like to reopen the ticket, but please
[https://docs.djangoproject.com/en/stable/internals/contributing/triaging-
tickets/#closing-tickets follow the triaging guidelines with regards to
wontfix tickets] and take this to DevelopersMailingList (or
[https://forum.djangoproject.com/ Django Forum]) , where you'll reach a
wider audience and see what other think.
> But wouldn't it be kind of neat if update_or_create could pass along
additional kwargs to your custom save method?
We don't add new options if it's not something useful for many folks.
> I know I have plenty of use cases for that.
You didn't not present any specifics. Please be prepared to share concrete
example in a forum/mailing list thread, if you will decide to start a
discussion.
--
Ticket URL: <https://code.djangoproject.com/ticket/35014#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018c3d6892e1-2996b077-6a2d-458d-8574-efc2af6d6e47-000000%40eu-central-1.amazonses.com.
