#35793: Add support for atomic upserts
-------------------------------------+-------------------------------------
Reporter: Storm Heg | Owner:
| YashRaj1506
Type: New feature | Status: assigned
Component: Database layer | Version:
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
Thanks for the backends support investigation, that's quite useful!
> I use Inserted here, but it could just as well be Excluded.
I think `Excluded` would be preferable as its closer to the SQL naming and
refers to the conflicting row. I feel like `Inserted` is ambiguous as it's
effectively ''tentatively inserted but failed''.
--
Ticket URL: <https://code.djangoproject.com/ticket/35793#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 visit
https://groups.google.com/d/msgid/django-updates/01070198d7581567-c3e4964d-7ee9-44ef-851b-13046573e488-000000%40eu-central-1.amazonses.com.
