From 36b45611bcaee0ba55b40384f29e8b6546f109bb Mon Sep 17 00:00:00 2001 From: Juan Catalano Date: Mon, 18 Mar 2013 20:54:24 -0300 Subject: [PATCH] Added warn note to docs about MySQL issues with 0000-00-00 date strings MySQL accepts 0000-00-00 as a valid date but MySQLdb converts those values into None. So there will be problems for instance if trying to transport the data using dumpdata/loaddata. This patch refs #6642 that has been closed as wontfix since this is a particular problem of MySQL. --- docs/ref/databases.txt | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt index 6d4e1663bf9..395abd90dd1 100644 --- a/docs/ref/databases.txt +++ b/docs/ref/databases.txt @@ -241,6 +241,14 @@ required for full MySQL support in Django. 1.2.1p2 or newer, then delete the ``sets.py`` file in the MySQLdb directory that was left by an earlier version. +.. note:: + There are known issues with the way MySQLdb converts date strings into + datetime objects. Specifically, date strings with value 0000-00-00 are valid for + MySQL but will be converted into None by MySQLdb. + + This means you should be careful while using loaddata/dumpdata with rows + that may have 0000-00-00 values, as they will be converted to None. + .. _MySQLdb: http://sourceforge.net/projects/mysql-python Creating your database