#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 |
---------------------------------------------+------------------------------
Changes (by russellm):
* needs_better_patch: 0 => 1
* milestone: => 1.3
Comment:
I think you've tried to solve this in the wrong place. Rather than fixing
this at the level of the database backend, it seems to me that the
solution lies in fixing the test runner's setup_databases call. There is
already some handling for avoiding duplicate database setup (via the
handling for the TEST_MIRROR setting); it seems to me that the problem
described here is really just an TEST_MIRROR that is implied because the
database name is the same.
So - if we refactor the handling of TEST_MIRROR so that we pre-evaluate
the list of database that need to be created and the list that needs to be
redirected, we should be able to avoid this problem entirely.
Of course, this is just based on first inspection; there might be some
detail that I'm missing. I'll take a closer look later tonight (my time).
Also - bumping to 1.3 milestone because of the potential for unintentional
data loss.
--
Ticket URL: <http://code.djangoproject.com/ticket/14415#comment:4>
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.
