django.git/django/db/models/query.py, branch 1.5.8 django http://cgit.adnoto.dev/django.git/atom?h=1.5.8 2013-09-14T07:03:03Z Fixed #21102 -- pickling a QuerySet with prefetches twice 2013-09-14T07:03:03Z Minjong Chung mjipeo@gmail.com 2013-09-13T12:18:50Z urn:sha1:e66fe357b2324f984e91392286b3b0e6b5dd627e Fixed the bug that a QuerySet that prefetches related objects cannot be pickled and unpickled more than once (The second pickling attempt raises an exception). Added a new test for the queryset pickling idempotency. The bug was introduced by bac187c0d8e829fb3ca2ca82965eabbcbcb6ddd5. [1.5.x] Optimisation in prefetch_related_objects 2013-07-27T22:02:57Z Luke Plant L.Plant.98@cantab.net 2013-05-24T10:19:44Z urn:sha1:a2eb2195567e645c58ec20c382294b62640b9ea1 Backport of 17559e6eb0 from master [1.5.x] Fixed #19607 - prefetch_related crash 2013-07-27T21:59:27Z Luke Plant L.Plant.98@cantab.net 2013-05-24T09:01:34Z urn:sha1:00b39e0145c5b9117503b20bba74948294a30e5a Thanks to av@rdf.ru and flarno11@yahoo.de for the report. Backport of 4fd94969d8 from master [1.5.x] Fixed prefetch_related + pickle regressions 2013-05-21T08:45:24Z Anssi Kääriäinen akaariai@gmail.com 2013-05-21T08:06:49Z urn:sha1:bac187c0d8e829fb3ca2ca82965eabbcbcb6ddd5 There were a couple of regressions related to field pickling. The regressions were introduced by QuerySet._known_related_objects caching. The regressions aren't present in master, the fix was likely in f403653cf146384946e5c879ad2a351768ebc226. Fixed #20157, fixed #20257. Also made QuerySets with model=None picklable. [1.5.x] Fixed #20278 -- ensured .get() exceptions do not recurse infinitely 2013-05-20T16:05:43Z Anssi Kääriäinen akaariai@gmail.com 2013-05-20T15:45:24Z urn:sha1:0eddedf7db782a05e098c7024a9056aef7283b81 A regression caused by d5b93d3281fe93cbef5de84a52 made .get() error reporting recurse infinitely on certain rare conditions. Fixed this by not trying to print the given lookup kwargs. Backpatch of 266c0bb23e9d64c47ace4d162e582febd5a1e336 [1.5.x] Revert "Fixed #19895 -- Made second iteration over invalid queryset raise an exception too" 2013-03-20T09:43:14Z Claude Paroz claude@2xlibre.net 2013-03-20T09:32:13Z urn:sha1:b91067d9aa42e31d4375e00a703beaacdb30d608 This reverts commit d1e87eb3baf75b1b6a0ada46a9b77f7e347cdb60. This commit was the cause of a memory leak. See ticket for more details. Thanks Anssi Kääriäinen for identifying the source of the bug. [1.5.x] Fixed #19895 -- Made second iteration over invalid queryset raise an exception too 2013-02-23T20:39:05Z Grzegorz Nosek root@localdomain.pl 2013-02-23T19:59:09Z urn:sha1:d1e87eb3baf75b1b6a0ada46a9b77f7e347cdb60 When iteration over a queryset raised an exception, the result cache remained initialized with an empty list, so subsequent iterations returned an empty list instead of raising an exception Backport of 2cd0edaa477b327024e4007c8eaf46646dcd0f21 from master. [1.5.x] Fixed #19720 -- Oracle ordering related delete regression 2013-02-10T17:58:22Z Anssi Kääriäinen akaariai@gmail.com 2013-02-10T17:49:28Z urn:sha1:b18ad807e0b7f34df4e4b319af128883a54c03bd When a query had a complex where condition (a condition targeting more than the base table) a subquery was used for deletion. However, the query had default ordering from the model's meta and Oracle doesn't work with ordered subqueries. The regression was caused by fast-path deletion code introduced in 1cd6e04cd4f768bcd4385b75de433d497d938f82 for fixing #18676. Thanks to Dylan Klomparens for the report. Backpatch of 8ef3235034a1a7616714a5d61486dc68536f74ee [1.5.x] Fixed typos in docs and comments 2013-01-29T17:58:24Z Tim Graham timograham@gmail.com 2013-01-29T15:45:40Z urn:sha1:5da6ce11edb60319c014c07c40b03674ea89de4c Backport of ee26797cff from master Fixed #19426 -- Adapted EmptyQuerySet.distinct signature 2013-01-03T17:03:51Z Claude Paroz claude@2xlibre.net 2013-01-03T17:03:51Z urn:sha1:a893ee3315d6a134b46ff8c36c44a8efbbe34886 1.5-only change, as EmptyQuerySet will be refactored in 1.6. Thanks hongshuning@gmail.com for the patch.