#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 timgraham):
I guess it's a good point about whether we should add the check now that
MySQL is changing the default of `STRICT_TRANS_TABLES`. As Shai said,
presumably going forward then, this check will only trigger for users
configuring the database otherwise, so I wonder if it adds any value
except for users of older versions of MySQL?
--
Ticket URL: <https://code.djangoproject.com/ticket/26351#comment:14>
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.35479517ef19f5700cdfd5ac68320c3d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
