On 08/04/2010 06:08 PM, Xavier Ordoquy wrote:
The second database should be created. Maybe you want to double check you setup a database router.
I *do* have a database router. The router makes sure that 5 tables end up in the second database (and the others end up in the default database).
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 :-)
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.
