On Fri, Jun 4, 2010 at 4:54 PM, burc...@gmail.com <burc...@gmail.com> wrote:
> Hi Russell,
>
> I strongly disagree with your and Adrian vision of whether conventions
> are good or not.
> But I won't comment that any further. There are your political
> decisions, and I have no single bit of control on them.
> I know that it's impossible to persuade you, so why should I spend my
> time doing this.
>
> However, you didn't tell anything on the problem that was the main
> reason why I wrote this app.
> Additive variables.
>
> DATABASES, DATABASE_ROUTERS, MIDDLEWARE, etc.
> Do you think situation will change with them?
>
> In example, I want few of my apps to work with their own databases.
> They need to install their database into DATABASES and their router
> into DATABASE_ROUTERS.
>
> How would you do that?
>
Apps shouldn't configure what databases they use, the project should
configure what database an app uses.
If the app is multi-db aware, and wants its own database, it should
use a value from settings to determine the DB to use, and the project
manager configures both the DB name, and the entry in DATABASES to
give it the right configuration.
Eg:
settings.py:
FOO_APP_DB_NAME = 'fooapp'
DATABASES = { 'default': { .. }, 'fooapp': { ... }, }
Cheers
Tom
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
