#13946: Database caching doesn't account for multiple databases
-----------------------------------+----------------------------------------
Reporter: tiemonster | Owner: nobody
Status: new | Milestone: 1.3
Component: Cache system | Version: 1.2
Resolution: | Keywords: multidb database caching
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------+----------------------------------------
Comment (by russellm):
It's not just the overhead I'm concerned about (although that is a mild
concern). It's the mechanics of getting a model installed.
* The database table name is only available via settings.py
* and only then *if* the database cache backend is being used;
* there isn't a models.py to put the model file in.
I suppose the other approach would be to use the router, but use a dummy
model that can be clearly identified - i.e, a class that quacks like a
normal Django model, but is actually a representation of the database
cache model. The 'cache model' wouldn't actually be used for database
operations; it would just provide the metadata that the router requires.
That way we step outside the usual app/models registration process, but
can use the simple interface for routing purposes.
--
Ticket URL: <http://code.djangoproject.com/ticket/13946#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 [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.
