#9307: Pickling support for Oracle Query classes
---------------------------------------------------+------------------------
Reporter: mtredinnick | Owner: mtredinnick
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: 1.0
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by mtredinnick):
* stage: Unreviewed => Accepted
Comment:
Urgh. I really, really want to avoid that type of code and I removed it
for that reason. It's ugly. The normal class is `Query`. It shouldn't have
to enter the witness-protection program and undergo a name change just
because we need to override it somewhere else.
There must be some other solution that is local to the Oracle (and other
custom) backend code. I'll try to work out a better way to test this
locally, perhaps by making a fake PostgreSQL class or something to see
what I can come up with. I hadn't thought of the name clash issue and
didn't check that out in my parallel development attempt.
Thanks for testing so quickly and giving feedback, though. That helps.
--
Ticket URL: <http://code.djangoproject.com/ticket/9307#comment:3>
Django <http://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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
