Hi all,
One of the use cases that may be common for multiple database support is being
able to combine multiple Django applications that require different databases
into a single site. This is exactly what I need to do for one project. This
can be done with the new multiple database support, but it feels heavy handed
to me to require the "integrator" go through all of the application code and
insert "using" specifiers. I also get nervous to about missing some places
where it would be required.
I've reviewed the code related to the selection of the default database and
think that it wouldn't be too hard to make it possible to do application
specific defaults to database settings. It would mostly be refactoring the
django.db.DEFAULT_DB_ALIAS constant into a function, and then deciding the best
way to allow the user to specify a default database per application in the
settings file.
Has there been any consideration or discussion of this type of functionality?
Regards,
Bill
--
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.
