Hi Ramiro, I've tried that, but those notes are just to flush the second db, but in this case, the issue is that the database is not even getting created at all.
On Nov 15, 8:59 am, Ramiro Morales <cra...@gmail.com> wrote: > On Sun, Nov 14, 2010 at 6:41 PM, churris <churri...@hotmail.com> wrote: > > I'm using django 1.2, and I had to setup a second database on my > > project. As soon as I setup the second connection and the router on my > > project, all my test cases which aren't even referring to that second > > database started to fail. Running the application works fine, syncdb > > works fine, is just the testing (unit testing) that I'm having > > problems. It appears to me that the second database is never created, > > and even if I create that manually as (test_mydbname) it keeps > > failing. > > > Is this supported? > > Did you find (and apply what is suggests) the relevant notes to the > multi-DB functionality in the testing docs?: > > http://docs.djangoproject.com/en/1.2/topics/testing/#multi-database-s... > > -- > Ramiro Morales -- 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.
