dumpdata doesn't honor router information
|Reported by:||Russell Keith-Magee||Owned by:||nobody|
|Component:||Database layer (models, ORM)||Version:||1.2-beta|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
Reported by wizard_2/Francis on django-users:
loaddata uses router.allow_syncdb() to determine whether an object should be loaded from a fixture. dumpdata, however, doesn't do the same when outputting a fixture. This can lead to "Table doesn't exist" database errors when a router indicates that a specific model shouldn't be available on a given database, but dumpdata tries to dump the model anyway.