#23871: MySQL database backend shouldn't promote warnings to exceptions in DEBUG
mode
-------------------------------------+-------------------------------------
Reporter: timgraham | Owner: timgraham
Type: | Status: new
Cleanup/optimization | Version: master
Component: Database | Keywords:
layer (models, ORM) | Has patch: 1
Severity: Normal | Needs tests: 0
Triage Stage: Accepted | Easy pickings: 0
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Quoting Aymeric in the [https://groups.google.com/d/topic/django-
developers/FwMI7_qcXHU/discussion django-developers] thread:
- 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.
--
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/052.09504c35d98d1fc762e9482f9a2e3f5f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
