#15063: multi_db flag on TestCase causes invalid error reporting
------------------------------------+---------------------------------------
Reporter: dcramer | Owner: nobody
Status: closed | Milestone:
Component: Uncategorized | Version: 1.2
Resolution: invalid | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by russellm):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
You appear to be describing a situation where a test database can't
synchronize all the tables it should have, and as a result, fixture
loading fails.
For my money, that situation *should* raise errors.
I'm not sure I see how this is related to multi-db. Setting multi-db=True
increases the number of databases that will be synchronized, but it
doesn't change the way individual databases are synchronized. If you get
this problem with multi-db, you should be able to reproduce it with a
single database under the right conditions.
Closing invalid; if I've missed the point, feel free to reopen and provide
more detail. For the record, you should also feel free to provide
sufficient detail when you open a ticket in the first place :-)
--
Ticket URL: <http://code.djangoproject.com/ticket/15063#comment:1>
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
