diff options
| author | Juan Catalano <jc@streema.com> | 2013-03-18 20:54:24 -0300 |
|---|---|---|
| committer | Juan Catalano <jc@streema.com> | 2013-03-18 21:05:38 -0300 |
| commit | 36b45611bcaee0ba55b40384f29e8b6546f109bb (patch) | |
| tree | de1ac750f097f3db4994eca761b43d31d60c0937 /docs | |
| parent | 31b5275235bac150a54059db0288a19b9e0516c7 (diff) | |
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.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/ref/databases.txt | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt index 6d4e1663bf..395abd90dd 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 |