On 08/05/2010 07:27 AM, Xavier Ordoquy wrote:
I'll do some experimenting with django versions. I clearly remember adding
code to my router to allow django to create those 5 tables in my second
database, so it *did* work. Perhaps 1.2.1 broke something that
1.2betasomething did right? Gotta drink wine with my wife now, I'll test
tomorrow :-)
Could it be that you weren't using doctest before and that there is some issue
with doctest and multi db support ?
I must say I haven't used doctests with multidb yet.
Also I'm not sure I understood your issue correctly.
When you state that the second database isn't created, you mean the tables are
not created right ?
Yes, the tables aren't created.
I found it, sigh. I added the following lines to my settings.py
according to one of those django-with-hudson-integration articles (like
http://www.caktusgroup.com/blog/2010/03/08/django-and-hudson-ci-day-1/):
TEST_RUNNER = 'xmlrunner.extra.djangotestrunner.run_tests'
TEST_OUTPUT_DESCRIPTIONS = True
TEST_OUTPUT_DIR = 'xmlrunner'
Apparently that test runner doesn't work with the multi db setup. When
I removed those lines, the tests would work again. I really should have
spotted that by running the tests before and after making that config
change...
Ok, now I'll have to figure out a different way of getting xml output
(for hudson) out of django's tests.
Thanks,
Reinout
--
Reinout van Rees - rein...@vanrees.org - http://reinout.vanrees.org
Programmer at http://www.nelen-schuurmans.nl
"Military engineers build missiles. Civil engineers build targets"
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
