#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):
Okay. The `docs/ref/databases.txt` note in your patch recommends
`STRICT_TRANS_TABLES` as opposed to `STRICT_ALL_TABLES` or `'sql_mode':
'traditional'` as mentioned in the other ticket. If there's a reason to
prefer one or the other, I didn't see it discussed. Not a MySQL user
myself, just wanted to check about that.
[http://dev.mysql.com/doc/refman/5.7/en/sql-mode.html MySQL SQL mode
reference docs].
--
Ticket URL: <https://code.djangoproject.com/ticket/26351#comment:19>
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.014c208e66d792a4d8c550e94e83f6a8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
