From d3cf6cfacfb828faad4f4f97c904e259304649b3 Mon Sep 17 00:00:00 2001 From: Vajrasky Kok Date: Sun, 24 Nov 2013 21:12:22 +0800 Subject: 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. --- docs/releases/1.7.txt | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'docs') 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 -- cgit v1.3