On Tue, Dec 7, 2010 at 11:21 PM, mpaolini <[email protected]> wrote: > Maybe unrelated... > > have you had a look at #14662?
It's related, but in the sense that it's the manual manifestation of what #14799 needed to correct. The contenttype and auth post_syncdb handlers ignore --db by design -- they should be (and are) using the router to determine where content types should be written. If running `sycndb` on `other` causes an error because `default` doesn't exist, then that means you have a dependency in your database setup, and you need to run `sycndb` on `default` first. #14799 was the manifestation of this problem in the test suite. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
