- there's absolutely no reason to be more strict in development than in
production
- promoting warnings to exceptions in production would be subtly
backwards-incompatible
- you can enable this behavior in the MySQL configuration e.g. by enabling
Strict SQL Mode
--
Ticket URL: <https://code.djangoproject.com/ticket/23871>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Comment (by iljamaas):
Will fix #21163 too
Thanx for removing
--
Ticket URL: <https://code.djangoproject.com/ticket/23871#comment:1>
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"5bcd292098b4de7bb03ef778e24d9e2f433d0dae"]:
{{{
#!CommitTicketReference repository=""
revision="5bcd292098b4de7bb03ef778e24d9e2f433d0dae"
Fixed #23871 -- Removed promotion of MySQL warnings to errors in DEBUG
mode.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23871#comment:2>