#16865: get_or_create defaults to _for_write even when it's just reading
-------------------------------------+-------------------------------------
Reporter: Rick van Hattem | Owner: nobody
<Rick.van.Hattem@…> | Status: closed
Type: Bug | Version: 1.3
Component: Database layer | Resolution: wontfix
(models, ORM) | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: | Patch needs improvement: 0
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 1 |
-------------------------------------+-------------------------------------
Comment (by WoLpH):
If this case is such a problem, wouldn't a setting fix it? Or a parameter
for the `get_or_create` method?
There has to be some way to enable this within the ORM. Having to write
your own `try/except` every time you use it (especially with the required
savepoints) is quite the hassle.
--
Ticket URL: <https://code.djangoproject.com/ticket/16865#comment:18>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
