#14415: Multiple aliases for one database: testing problems
-------------------------------------+-------------------------------------
Reporter: shai | Owner: nobody
Type: Uncategorized | Status: new
Component: Testing framework | Version: master
Severity: Normal | Resolution:
Keywords: multidb, multiple | Triage Stage: Design
databases, multiple aliases | decision needed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by mgachhui):
Could you give an example where the tests currently fail? I'm not very
clear on the model separation.
--
Ticket URL: <https://code.djangoproject.com/ticket/14415#comment:18>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.6bc8e58159bb3c593b14ae05c0476798%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.