2014-11-17 10:45 GMT+01:00 Florian Apolloner <[email protected]>:
> Imo we should make those exceptions instead! Data truncation should never > be just a warning ;) > Those who think like you can use a database instead of MySQL ;-) I agree we should simply remove the code that promotes warnings to exceptions in DEBUG mode because : - 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 -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" 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]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CANE-7mUKPjoW%2B%3DtTUxPsywWZtkKUTWkPWEJRtv3AitZKBpL27Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
