#30199: get_or_create documentation encourages unsafe usage
--------------------------------------+------------------------------------
Reporter: Alex | Owner: Alex
Type: Cleanup/optimization | Status: assigned
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Tim Graham):
Since #27683 (Django 2.0), Django defaults to read committed and
[https://docs.djangoproject.com/en/dev/ref/databases/#mysql-isolation-
level the documentation] says, "Django works best with and defaults to
read committed rather than MySQL’s default, repeatable read. Data loss is
possible with repeatable read." The note about "REPEATABLE READ (the
default)" in `QuerySet.get_or_create()` is therefore incorrect and perhaps
obsolete.
--
Ticket URL: <https://code.djangoproject.com/ticket/30199#comment:4>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.9b229d85cd580767b19390ee4086435f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
