On Sat, Nov 10, 2012 at 3:57 AM, Christian Jensen <christ...@jensenbox.com>wrote:
> Hi, > > Has anyone run into an issue where dumpdata refers to the old auth model > and tries to dump its data? > > Here is what I am encountering: > > DEBUG 2012-11-09 11:49:46,363 util 8457 140488053692160 (0.002) SELECT > "auth_user"."id", "auth_user"."password", "auth_user"."last_login", > "auth_user"."username", "auth_user"."first_name", "auth_user"."last_name", > "auth_user"."email", "auth_user"."is_staff", "auth_user"."is_active", > "auth_user"."is_superuser", "auth_user"."date_joined" FROM "auth_user" > ORDER BY "auth_user"."id" ASC; args=() > > CommandError: Unable to serialize database: relation "auth_user" does not > exist > LINE 1: ...r"."is_superuser", "auth_user"."date_joined" FROM "auth_user... > > Short answer -- no, I haven't run into this problem. I've tried running dump data with a custom User model, and it worked for me; can you provide a minimal project setup to reproduce this problem? 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 django-developers@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.
