#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):
After a second look: Yes, the new TEST_MIRROR behavior seems to be correct
and even required to preserve production semantics (interleaved operations
on master and slave with no commit may yield different result in
production and test with current code).
One other note, though: PORT needs to be treated just like HOST,
orthogonal to the !SqlServer issue mentioned in my earlier comment.
If there is an easy way to provide tests for these issues, I'd like to do
that.
Thanks,
Shai.
--
Ticket URL: <http://code.djangoproject.com/ticket/14415#comment:9>
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.
