#10839 closed (fixed)
Pickling queryset.query doesn't work for gis models on Oracle
Reported by: | Jani Tiainen | Owned by: | jbronn |
---|---|---|---|
Component: | GIS | Version: | dev |
Severity: | Keywords: | oracle gis | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | yes | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description (last modified by )
If I pickle queryset.query which is GIS model I get following results (using Oracle as database):
qs = MyModel.objects.filter(id=12345)
before pickling:
>>> qs.query <django.contrib.gis.db.models.sql.query.GeoQuery object at 0x0199FB90> >>> qry_str = pickle.dumps(qs.query) >>> qry = pickle.loads(qry_str) >>> qry <django.db.backends.oracle.query.OracleQuery object at 0x019C3F70>
Somehow query object has changed. It works as expected on non GIS models.
Attachments (1)
Change History (6)
comment:1 by , 16 years ago
Description: | modified (diff) |
---|
comment:2 by , 16 years ago
Keywords: | oracle gis added |
---|---|
Summary: | Pickling queryset.query doesn't work for gis models → Pickling queryset.query doesn't work for gis models on Oracle |
by , 16 years ago
Attachment: | geoquery_pickle_orcl.diff added |
---|
comment:3 by , 16 years ago
Needs tests: | set |
---|---|
Owner: | changed from | to
comment:4 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:5 by , 16 years ago
Note:
See TracTickets
for help on using tickets.
Initial stab at this patch.