#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: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by shaib):
If MySql has already made `STRICT_TRANS_TABLES` the default, I suggest we
do the same. In a few versions, when MySql 5.5 and 5.6 reach EOL, we'll be
there anyway.
This comment is almost orthogonal to the solution of database checks,
which is a generally needed feature. The only point of contact is the
check for `STRICT_TRANS_TABLES` itself, since if we default to it, a user
who explicitly chose otherwise doesn't need to be warned about their
choice.
--
Ticket URL: <https://code.djangoproject.com/ticket/26351#comment:12>
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/065.d0cfd68e07147866db92237b12db553f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
