The default setting defines the application-wide db connection. The Manager mechanism is for overriding the default connection.
Selecting the db via signals makes no sense to me, however a mapping between apps and databases in settings is worth a moment of thought as a possible supplement to the Manager approach. Rock P.S. for Simon: I haven't spotted any obvious problems with the proposal so far. My initial reaction is that I like it. Good work! On Sep 10, 1:13 pm, "Justin Fagnani" <[EMAIL PROTECTED]> wrote: > For application-wide db connections, I think it'd be much easier and > more portable to choose the connection in settings.py rather than in a > Model. > > Manager.get_connection() is a great idea, but would it also make sense > to allow selecting the db via signals? That way you could make the > decision without modifying an app. > > -Justin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
