Changes between Initial Version and Version 2 of Ticket #18674


Ignore:
Timestamp:
Jul 27, 2012, 3:47:17 AM (12 years ago)
Author:
Anssi Kääriäinen
Comment:

What is likely happening here is that you have a queryset created in 1.3 stored in the session. When Django tries to load and evaluate it, the stored queryset doesn't have the prefetch stuff in it, as 1.3 didn't have it. I am not an expert of the pickle protocol, so it might be this explanation is plain wrong...

This ticket is likely invalid. But, should we advice people to clear their sessions on Django version upgrades? If the above guess is correct, similar errors (which are hard to debug) are bound to happen...

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #18674

    • Property Resolutioninvalid
    • Property Status newclosed
  • Ticket #18674 – Description

    initial v2  
    11I suspect this occurs when session has expired, or something similar and may be related to a change of API in django 1.4:
    2 
     2{{{
    33AttributeError at /
    44'QuerySet' object has no attribute '_prefetch_related_lookups'
     
    4343Exception Type: AttributeError at /
    4444Exception Value: 'QuerySet' object has no attribute '_prefetch_related_lookups'
    45 
     45}}}
    4646DB is MySQL.
Back to Top