#26351: Recommend enabling MySQL's STRICT_TRANS_TABLES to prevent silent
truncation
-------------------------------------+-------------------------------------
Reporter: zhebrak | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Documentation | Version: 1.9
Severity: Normal | Resolution:
Keywords: get_or_create, | Triage Stage: Accepted
max_length |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* type: Bug => Cleanup/optimization
* component: Database layer (models, ORM) => Documentation
* stage: Unreviewed => Accepted
Comment:
I think there's not much Django can do except to recommend enabling
`STRICT_TRANS_TABLES` to avoid silent truncation in the MySQL database
notes in `docs/ref/databases.txt`. It's enabled by default for MySQL 5.7+.
--
Ticket URL: <https://code.djangoproject.com/ticket/26351#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.697037b5072a6c48dc709ce96fc0ee30%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
