Sorry I haven't kept up with this discussion; althugh the issue has now been closed, I'd like to say,
On Sunday 05 December 2010 23:08:28 Nick Phillips wrote: > On Sat, 2010-12-04 at 11:56 +0800, Russell Keith-Magee wrote: > > Option 4: Introduce a per-database setting -- TEST_DEPENDENCIES -- > > Seems a lot more general than just test-related, anyway; I'd have > thought it would make more sense to see (and name, and document) it as a > general dependency of one database on the other - so > creation/updates/migrations should all always happen in an order which > takes any defined dependencies into account. I'm guessing that the test > setup just happens to be the only place (within Django itself) where any > of these processes are automated across multiple DBs at the moment? > I fully agree. Why is it "test_dependencies" and not plain "dependends_on" ? -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
