#1142: Support for multiple database connections
---------------------------------+------------------------------------------
Reporter: Simon Willison | Owner: adrian
Status: new | Component: Database wrapper
Version: | Resolution:
Keywords: multiple database | Stage: Design decision needed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
---------------------------------+------------------------------------------
Comment (by [EMAIL PROTECTED]):
Is multiple database support going to implemented?
At least in my case, I was looking at Django for an application for my
company, but it will need to access at least 2 databases. The main one,
plus a database from another product over which we have no control and
can't change.
We would actually like it to be 3 databases with the 3rd one being for
reporting data. We prefer to keep reporting data in a separate database
for performance purposes and for scalability, but if absolutely necessary,
we would put it in the dsame database as the main data. That still leaves
us with at least 2 databases.
We have another app that was done in Java with Hibernate and Hibernate is
currently accessing 4 databases from within the same app.
--
Ticket URL: <http://code.djangoproject.com/ticket/1142#comment:24>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
