#33343: update_or_create seems to issue wrongly limited query to the database
-------------------------------------+-------------------------------------
Reporter: Florian Apolloner | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Florian Apolloner):
Ah, I mixed up queries with and without `get()`, my bad. Reminds me that I
really should fix `update_or_create` at some point to do what I expect:
Namely update first and only create as fallback. /me goes to reject a PR
that tries to introduce `update_or_create` in our codebase instead of
proper update & on conflict inserts :D
--
Ticket URL: <https://code.djangoproject.com/ticket/33343#comment:2>
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/066.5fde489c32892320cbeb4f9ff31f4957%40djangoproject.com.
