#31689: Docs should warn about ignore_conflicts making MySQL tinker with your
data
-------------------------------------+-------------------------------------
Reporter: Tobias Krönke | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Documentation | Version: 3.0
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tobias Krönke):
I was considering this, too. However the description is rather vague not
really mentioning what "ignoring a failure" could mean and thereby easily
implying that the row is simply not inserted. If you don't want to pollute
this method's documentation, it could also be added to
https://docs.djangoproject.com/en/3.0/ref/databases/#setting-sql-mode to
make users aware of exceptions to strict mode.
--
Ticket URL: <https://code.djangoproject.com/ticket/31689#comment:3>
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/062.6be23ca79f460fa3acaa47c0a136d31d%40djangoproject.com.
