I notice that this problem gets discussed occasionally but with no proper resolution, so I felt obliged to raise it again, as the consequences are quite serious for MySQL users.
When MySQL issues a warning, Django sometimes raises an exception. This is discussed in https://code.djangoproject.com/ticket/12293, which is marked as wontfix. The main problem is that the behaviour is different depending whether DEBUG is True or not. This leads to problems with testing and deployment that in an extreme case could cause data loss. A secondary problem is that the exception in question isn't being caught and re-thrown as a Django exception, so that code that wants to deal with such scenarios must catch a MySQL-specific exception, tying us to the one database back-end. For me, the right choice would be to make this configurable, and completely independent of the DEBUG setting. The right default would be to ignore warnings, as in general that's how most programs coding against MySQL would expect to treat them. Most people I would argue would expect a warning to be ignored and for processing to continue. *Please* can this wontfix be re-considered -- the interwebs appear to be full of people getting caught out by this (if it will help the case, I can list numerous references!) TIA George -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/Zj13E62NFOYJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
