Hi, >> So far, the only issue I found with testing on multi database is that django >> 1.2 expects all the tables are created on the second database which may not >> always be the case (bug reported, I just uploaded a patch for that). > > Which patch/ticket is that? With my router, the second database is > definitively not filled with all tables: just the 5 that are supposed to be > in there. > > 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 ? Regards, Xavier. -- 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.
