innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Documented backwards incompatibilities in the two previous commits.

This commit is contained in:
Aymeric Augustin 2013-02-11 22:30:22 +01:00
parent 91ef84713c
commit b4351d2890
2 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/ref/models/querysets.txt
View File

@ -614,6 +614,8 @@ object. If it's ``None``, Django uses the :ref:`current time zone
<default-current-time-zone>`. It has no effect when :setting:`USE_TZ` is <default-current-time-zone>`. It has no effect when :setting:`USE_TZ` is
``False``. ``False``.
.. _database-time-zone-definitions:
.. note:: .. note::
This function performs time zone conversions directly in the database. This function performs time zone conversions directly in the database.

10
docs/releases/1.6.txt
View File

@ -102,6 +102,16 @@ Backwards incompatible changes in 1.6
list of :class:`~datetime.date`. It used to return a list of list of :class:`~datetime.date`. It used to return a list of
:class:`~datetime.datetime`. :class:`~datetime.datetime`.
* The :attr:`~django.contrib.admin.ModelAdmin.date_hierarchy` feature of the
admin on a :class:`~django.db.models.DateTimeField` requires time zone
definitions in the database when :setting:`USE_TZ` is ``True``.
:ref:`Learn more <database-time-zone-definitions>`.
* Accessing ``date_list`` in the context of a date-based generic view requires
time zone definitions in the database when the view is based on a
:class:`~django.db.models.DateTimeField` and :setting:`USE_TZ` is ``True``.
:ref:`Learn more <database-time-zone-definitions>`.
* Model fields named ``hour``, ``minute`` or ``second`` may clash with the new * Model fields named ``hour``, ``minute`` or ``second`` may clash with the new
lookups. Append an explicit :lookup:`exact` lookup if this is an issue. lookups. Append an explicit :lookup:`exact` lookup if this is an issue.