#28503: Updating 1.10 to 1.11 object has no attribute
'select_for_update_skip_locked'
-------------------------------------+-------------------------------------
Reporter: Jorge Cadena Argote | Owner: nobody
Type: Bug | Status: closed
Component: Uncategorized | Version: 1.11
Severity: Normal | Resolution: invalid
Keywords: update version | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* status: new => closed
* resolution: => invalid
Comment:
As pointed at by the warnings you tried re-using pickled `QuerySet`s
between Django versions
{{{
/home/aztrock/workspace/env/local/lib/python3.5/site-
packages/redis_cache/serializers.py:42: RuntimeWarning: Pickled model
instance's Django version 1.10.6 does not match the current version
1.11.4.
return pickle.loads(force_bytes(value))
/home/aztrock/workspace/env/local/lib/python3.5/site-
packages/redis_cache/serializers.py:42: RuntimeWarning: Pickled queryset
instance's Django version 1.10.6 does not match the current version
1.11.4.
return pickle.loads(force_bytes(value))
}}}
From https://docs.djangoproject.com/en/1.11/ref/models/querysets
/#pickling-querysets
> **You can’t share pickles between versions**
>
> Pickles of QuerySets are only valid for the version of Django that was
used to generate them. If you generate a pickle using Django version N,
there is no guarantee that pickle will be readable with Django version
N+1. Pickles should not be used as part of a long-term archival strategy.
>
> Since pickle compatibility errors can be difficult to diagnose, such as
silently corrupted objects, a RuntimeWarning is raised when you try to
unpickle a queryset in a Django version that is different than the one in
which it was pickled.
--
Ticket URL: <https://code.djangoproject.com/ticket/28503#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.01866b3309b36ebec6be7eb4143a07a1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
