diff options
| author | Vajrasky Kok <sky.kok@speaklikeaking.com> | 2013-11-24 21:12:22 +0800 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2014-02-06 05:16:40 -0500 |
| commit | d3cf6cfacfb828faad4f4f97c904e259304649b3 (patch) | |
| tree | ae44bc63cc45a144edbec26bb5590b8225e70233 /docs | |
| parent | b22d6c47a7e4c7ab26a8b7b033d11fa6743aae86 (diff) | |
Fixed #17713 -- Renamed BaseDatabaseFeatures.allows_primary_key_0 to allows_auto_pk_0.
MySQL does allow primary key with value 0. It only forbids autoincrement
primary key with value 0.
Thanks Claude Paroz for the report.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/releases/1.7.txt | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/releases/1.7.txt b/docs/releases/1.7.txt index e802f257ae..a51c3dc981 100644 --- a/docs/releases/1.7.txt +++ b/docs/releases/1.7.txt @@ -1010,6 +1010,12 @@ Miscellaneous to ``False``). If you maintain a custom database backend, you should check that method. +* The ``django.db.backends.BaseDatabaseFeatures.allows_primary_key_0`` + attribute has been renamed to ``allows_auto_pk_0`` to better describe it. + It's ``True`` for all database backends included with Django except MySQL + which does allow primary keys with value 0. It only forbids *autoincrement* + primary keys with value 0. + .. _deprecated-features-1.7: Features deprecated in 1.7 |
