Django/django
11
0
Fork 0
Code Pull Requests Projects Releases Activity

Added changes missing from previous commit.

Browse Source 
Sorry.
This commit is contained in:
Aymeric Augustin 2013-03-24 14:30:04 +01:00
parent e16c48e001
commit e12aad2d57
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/releases/1.6.txt
View File

@ -298,13 +298,13 @@ connections.
When a :class:`~django.db.models.BooleanField` doesn't have an explicit When a :class:`~django.db.models.BooleanField` doesn't have an explicit
:attr:`~django.db.models.Field.default`, the implicit default value is :attr:`~django.db.models.Field.default`, the implicit default value is
``None``. In previous version of Django, it was ``False``, but that didn't ``None``. In previous version of Django, it was ``False``, but that didn't
represent accurantely the lack of a value. represent accurately the lack of a value.
Code that relies on the default value being ``False`` may raise an exception Code that relies on the default value being ``False`` may raise an exception
when saving new model instances to the database, because ``None`` isn't an when saving new model instances to the database, because ``None`` isn't an
acceptable value for a :class:`~django.db.models.BooleanField`. You should acceptable value for a :class:`~django.db.models.BooleanField`. You should
either specify ``default=False`` explicitly on the field definition, or ensure either specify ``default=False`` in the field definition, or ensure the field
the field is set to ``True`` or ``False`` before saving the object. is set to ``True`` or ``False`` before saving the object.
Translations and comments in templates Translations and comments in templates
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~