#31689: Warn that bulk_create()'s ignore_conflicts option ignores not only
duplicate keys on MySQL.
--------------------------------------+------------------------------------
Reporter: Tobias Krönke | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 3.0
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
--------------------------------------+------------------------------------
Changes (by felixxm):
* stage: Unreviewed => Accepted
Comment:
Agreed. It is really unexpected that `ignore_conflicts` ignores also bunch
of other errors. I don't think we should document this specific use case,
I would add a short warning (to the
[https://docs.djangoproject.com/en/stable/ref/models/querysets/#django.db.models.query.QuerySet.bulk_create
bulk_create() docs]) that MySQL ignores not only duplicate keys but also
other errors, with a reference to [https://dev.mysql.com/doc/refman/8.0/en
/sql-mode.html#ignore-strict-comparison the MySQL docs].
--
Ticket URL: <https://code.djangoproject.com/ticket/31689#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.0e05a60ebffeb5e848289d04a3d56dd1%40djangoproject.com.
