1401272 - Use MySQL Strict Mode (django_mysql.W001)

Status: RESOLVED FIXED

(developer.mozilla.org Graveyard :: General, enhancement, P2)

Description

[John Whitlock [:jwhitlock]]

What did you do?
================
Ran a command (./manage.py make_sitemaps) with warnings enabled.

What happened?
==============
System check identified some issues:

?: (django_mysql.W001) MySQL Strict Mode is not set for database connection 'default'
	HINT: MySQL's Strict Mode fixes many data integrity problems in MySQL, such as data truncation upon insertion, by escalating warnings into errors. It is strongly recommended you activate it. See: http://django-mysql.readthedocs.org/en/latest/checks.html#django-mysql-w001-strict-mode

What should have happened?
==========================
No warnings should have been identified.

Is there anything else we should know?
======================================
More details are at:

http://django-mysql.readthedocs.org/en/latest/checks.html#django-mysql-w001-strict-mode

Enabling this feature may expose bugs in Kuma. Some may be detected by tests, and some detected at runtime. It should be enabled when there is time to rapidly fix the exposed bugs.

Comment 1

[John Whitlock [:jwhitlock]]

I thought I opened a more recent bug for this, but it is the original.

Here's my strategy:
1. Enable in development environment for a week, fix any issues.
2. Enable in staging, test
3. Enable in production

Comment 2

[John Whitlock [:jwhitlock]]

Deployed to staging and production. No integrity issues found.