#26351: Recommend enabling MySQL's STRICT_TRANS_TABLES to prevent silent
truncation
-------------------------------------+-------------------------------------
Reporter: zhebrak | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: 1.9
Severity: Normal | Resolution: fixed
Keywords: get_or_create, | Triage Stage: Ready for
max_length | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Claude Paroz <claude@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"f9a2a7db173b53f9cb0cd2d3def80d4eed72631c" f9a2a7d]:
{{{
#!CommitTicketReference repository=""
revision="f9a2a7db173b53f9cb0cd2d3def80d4eed72631c"
Fixed #26351 -- Added MySQL check to warn about strict mode option
Thanks Adam Chainz for the initial implementation in django-mysql.
Thanks Adam Chainz, Tim Graham, and Shai Berger for the reviews.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26351#comment:25>
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.492b910eb1f64ce1dcdb2cd828b233b8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
