#15580: DB cache backend uses LIMIT / OFFSET query for culling
----------------------------------------+----------------------
Reporter: ikelly | Owner: nobody
Status: new | Milestone:
Component: Cache system | Version: SVN
Resolution: | Keywords: oracle
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 |
----------------------------------------+----------------------
Changes (by russellm):
* stage: Unreviewed => Accepted
Comment:
This is obviously a limitation -- however, it's not clear to me what the
resolution should be. I really don't want to replace the internals of the
DB cache backend with the ORM just so that we can get LIMIT and OFFSET
support for Oracle. We may just need to introduce an 'Oracle' DB backend,
and specialize that one call.
--
Ticket URL: <http://code.djangoproject.com/ticket/15580#comment:2>
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 [email protected].
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.
