Trying not to repeat myself too much while arguing for my fast-fading favorite... :)
> Yeah, you really better, since I don't like it one bit :) > > Currently the settings file for lawrence.com has... (/me checks)... > 48 entries. You mean I've got to duplicate my database settings 48 > times!? Only if they use 48 different databases. Anything not in DATABASES would use the default connection. Any database settings that are shared among > 1 app could be put into a variable ... or the keys in DATABASES could be tuples. > I like the idea of keys in ``DATABASES`` being "identifiers" for the > database connection; this lets something like the following work:: > > from django import db > conn = db.get_connection("main") > > Which I very much like... Me too, but I don't know how to reconcile it with configuring which apps use which settings. I'd be equally happy with: from django import db conn = db.get_connection_for('myproj.myapp') Which is almost as good, with a little extra goodness in not having to remember anything but the app name to get the connection for that app. > That makes ``DATABASES`` the canonical location > for, well, database info, and that's good. Yes, definitely. JP --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---