On Jul 10, 2006, at 11:02 PM, [EMAIL PROTECTED] wrote:
> That wouldn't matter. Maybe if I take out some ellipses it'll be more
> clear:
>
> DATABASES = {
> 'ellington': { 'DATABASE_NAME': 'ellington',
> 'DATABASE_ENGINE': 'postgresql',
> # DATABASE_USER etc
> },
> 'myproj.myapp': { 'DATABASE_NAME': '/var/db/readonly.db',
> 'DATABSE_ENGINE': 'sqlite3'
> },
> }
>
> The key in DATABASES need not have any relation to the DATABASE_NAME
> setting it references. It seems I'm growing more partial to this as
> the
> simplest solution, so I'd better think of some compelling
> arguments. :)
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!?
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...
I know you don't like it, but the more I think about it the more I
like the idea of each database stanza providing a list of apps it
should be used for. That makes ``DATABASES`` the canonical location
for, well, database info, and that's good.
Jacob
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" 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-developers
-~----------~----~----~----~------~----~------~--~---
