> 2. Have a setting which lets you say "for model auth.User, use the
> get_connection method defined over here". This is made inelegant by
> the fact that settings shouldn't really contain references to actual
> function definitions, which means we would probably need to us a
> 'dotted.path.to.a.function', which is crufty.
The admin takes a registry-based approach to associate ModelAdmin
classes with Models. Could a similar approach work here?
myapp/connections.py:
from django.contrib.multidb import connection
from myapp.models import MyModel
class MyModelConnection(connection.ModelConnection):
def __call__(self):
... return a database connection ...
connection.register(MyModel, MyModelConnection)
I guess there's no reason even for MyModelConnection to be a class; a
callable would do.
Just a thought.
Cheers,
Dan
--
Dan Fairs <[EMAIL PROTECTED]> | http://www.stereoplex.com/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@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-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
