#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 claudep):
I'm +0 about forcing `STRICT_TRANS_TABLES`. I think the main advantage of
the check over forcing the setting is that we don't load each connection
creation on runtime with the cruft of SELECTing the variable to check its
current state. The other minor advantage is that people are still free to
configure their database at their will, even if I don't see now a use case
for that.
--
Ticket URL: <https://code.djangoproject.com/ticket/26351#comment:13>
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.ddbfccb50f71b15282989ec7afeb3cb6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
