#13835: enhancements in django.db.models to get info about additional tables
---------------------------------------------------+------------------------
Reporter: fetzig | Owner: nobody
Status: closed | Milestone:
Component: Database layer (models, ORM) | Version: 1.2
Resolution: wontfix | Keywords: cache,
johnny-cache
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by ptone):
* status: new => closed
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
* resolution: => wontfix
* stage: Unreviewed => Accepted
Comment:
according to johnny-cache author this has been resolved now in johnny-
cache:
from the cited issue page: http://bitbucket.org/jmoiron/johnny-
cache/issue/7/use-subselect-tables-in-query-cache-key
''"This is fixed for Django 1.2.x in r124:66db10d95f72 and for Django
1.1.x in r125:d2cdde498f99 without resorting to patching Django. The 1.2.x
fix should work for all future versions and across all database backends;
if you use 1.1.x and a non-OSS database backend like Oracle or MS SQL,
testing would be appreciated."''
--
Ticket URL: <http://code.djangoproject.com/ticket/13835#comment:1>
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
