#20429: Implementation of update_or_create
-------------------------------------+-------------------------------------
Reporter: tunixman | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 1
Has patch: 1 | Patch needs improvement: 1
Needs tests: 1 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by russellm):
* needs_better_patch: => 1
* stage: Unreviewed => Accepted
* needs_tests: => 1
* needs_docs: => 1
Comment:
Upsert is a fairly common idea; seems worthwhile to me.
Regarding implementation: there's a lot of common ground between
get_or_create and update_or_create, so I'm wondering if there should be
some common base implementation, rather than layering one over the other.
--
Ticket URL: <https://code.djangoproject.com/ticket/20429#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 post to this group, send email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
