#14415: Multiple aliases for one database: testing problems
---------------------------------------------+------------------------------
Reporter: shai | Owner: nobody
Status: new | Milestone: 1.3
Component: Testing framework | Version: 1.2
Resolution: | Keywords: multidb,
multiple databases, multiple aliases
Stage: Design decision needed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
---------------------------------------------+------------------------------
Comment (by shai):
@russelm -- Sorry, I had misread your original patch; you are right, the
connections seem to be handled correctly.
I'll look at it again tonight (Israel time), to comment on the change in
TEST_MIRROR handling.
One note, though, about adding HOST: While it is, as far as I know, good
enough for Django's officially supported DBMSs, it is not enough for
!SqlServer or Sybase, where a host includes a set of databases, each
containing a set of "schemata". Not sure if preparing support for this is
easy, and if not easy, if it is worthwhile, but I thought it's worth
mentioning.
--
Ticket URL: <http://code.djangoproject.com/ticket/14415#comment:8>
Django <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.
