From 75a9c8a5ef6408cd51fd75fc8aefb2e812e353a1 Mon Sep 17 00:00:00 2001 From: Jannis Leidel Date: Thu, 9 Feb 2012 18:56:49 +0000 Subject: Fixed #10793 -- Stopped caching paginator instances in sitemap classes to prevent stale sitemaps. Thanks, gnosek, krzysiumed and adam_przybyla. git-svn-id: http://code.djangoproject.com/svn/django/trunk@17468 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/releases/1.4.txt | 15 +++++++++++++++ 1 file changed, 15 insertions(+) (limited to 'docs') diff --git a/docs/releases/1.4.txt b/docs/releases/1.4.txt index e004aefd60..e0bef0b56e 100644 --- a/docs/releases/1.4.txt +++ b/docs/releases/1.4.txt @@ -1150,3 +1150,18 @@ settings file to list all your applications explicitly. This attribute was confusingly named ``HttpRequest.raw_post_data``, but it actually provided the body of the HTTP request. It's been renamed to ``HttpRequest.body``, and ``HttpRequest.raw_post_data`` has been deprecated. + +``django.contrib.sitemaps`` bugfix with potential performance implications +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +In previous versions the Paginator objects used in sitemap classes were +cached and could result in stale sitemap indexes. Removing this cache causes +new Paginator objects to be created and the +:attr:`~django.contrib.sitemaps.Sitemap.items()` method of the +:class:`~django.contrib.sitemaps.Sitemap` subclass to be called during every +sitemap-related request. + +If the :attr:`django.contrib.sitemaps.Sitemap.items()` method returns a +``QuerySet`` its length will be evaluated which may lead to extra database +queries. To mitigate the performance impact consider using the :doc:`caching +framework `. -- cgit v1.3