#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 russellm):
@shai - Good call on the HOST issue - I've made that change; new patch
incoming shortly.
However, regarding the connection issue - I'm unclear whether what you
consider correct behavior, and under what circumstances.
The 'connection copying' behavior is only performed for the TEST_MIRROR
case, and that behavior exists historically. To my mind, this is a bug;
using connection obtained from the alias that is a TEST_MIRROR shouldn't
affect transactions created using the connection that is being mirrored.
The new patch addresses this bug.
However, you seem to be implying that the same connection copying behavior
exists for connections with a copied settings dictionary, which isn't the
case. The patch I've provided causes your sample code to raise an
exception at "transaction.commit(using=alias2)", because the code isn't
under transaction management (for alias2) at that point.
Have I misunderstood something here?
--
Ticket URL: <http://code.djangoproject.com/ticket/14415#comment:7>
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.
