Browse files

Documented backwards incompatibilities in the two previous commits.

  • Loading branch information...
aaugustin committed Feb 11, 2013
1 parent 91ef847 commit b4351d2890cd1090d3ff2d203fe148937324c935
Showing with 12 additions and 0 deletions.
  1. +2 −0 docs/ref/models/querysets.txt
  2. +10 −0 docs/releases/1.6.txt
@@ -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
+.. _database-time-zone-definitions:
.. note::
This function performs time zone conversions directly in the database.
@@ -102,6 +102,16 @@ Backwards incompatible changes in 1.6
list of :class:``. It used to return a list of
+* 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
lookups. Append an explicit :lookup:`exact` lookup if this is an issue.

0 comments on commit b4351d2

Please sign in to comment.