From b4351d2890cd1090d3ff2d203fe148937324c935 Mon Sep 17 00:00:00 2001 From: Aymeric Augustin Date: Mon, 11 Feb 2013 22:30:22 +0100 Subject: [PATCH] Documented backwards incompatibilities in the two previous commits. --- docs/ref/models/querysets.txt | 2 ++ docs/releases/1.6.txt | 10 ++++++++++ 2 files changed, 12 insertions(+) diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index 3e9ef7b83f..f77f87dd8e 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -614,6 +614,8 @@ object. If it's ``None``, Django uses the :ref:`current time zone `. It has no effect when :setting:`USE_TZ` is ``False``. +.. _database-time-zone-definitions: + .. note:: This function performs time zone conversions directly in the database. diff --git a/docs/releases/1.6.txt b/docs/releases/1.6.txt index 933f4f111d..9594481b9f 100644 --- a/docs/releases/1.6.txt +++ b/docs/releases/1.6.txt @@ -102,6 +102,16 @@ Backwards incompatible changes in 1.6 list of :class:`~datetime.date`. It used to return a list of :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 `. + +* 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 `. + * Model fields named ``hour``, ``minute`` or ``second`` may clash with the new lookups. Append an explicit :lookup:`exact` lookup if this is an issue.