#28162: Documented solution to "MySQL Strict Mode is not set" warning doesn't
work
in MySQL 5.5
------------------------------------------+------------------------
Reporter: Robert Rollins | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.11
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
------------------------------------------+------------------------
The Django docs claim that you can get rid of this warning by adding the
following to your `DATABASES` setting:
{{{
'init_command': "SET sql_mode='STRICT_TRANS_TABLES'"
}}}
This does not work in MySQL 5.5.47. The warning doesn't go away.
However, adding ''this'' to `DATABASES` does get rid of the warning:
{{{
'OPTIONS': {
'sql_mode': 'STRICT_TRANS_TABLES',
}
}}}
I found this solution [http://stackoverflow.com/a/23023015/464318 here],
but it seems like it really should be in the docs. Unless this doesn't
work in newer MySQLs?
--
Ticket URL: <https://code.djangoproject.com/ticket/28162>
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/056.047ca59888fd6e09c849107734a703ff%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
