Hello,
On Sat, Nov 24, 2012 at 7:43 AM, Russell Keith-Magee
wrote:
> Hi Benoit,
>
> Like I said in my last response, I'm *not* seeing the problem. Saying "I'm
> seeing the problem" doesn't help me. Saying "I've got a custom User" doesn't
> help me either -- I've got a custom User (several, actual
Hi Benoit,
Like I said in my last response, I'm *not* seeing the problem. Saying "I'm
seeing the problem" doesn't help me. Saying "I've got a custom User"
doesn't help me either -- I've got a custom User (several, actually - a
test case extending AbstractUser and one extending AbstractBaseUser, pl
I have the same issue with django 1.5. I have a custom User model that
extends AbstractUser.
Regards
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-develope
On Sat, Nov 10, 2012 at 3:57 AM, Christian Jensen
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
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"."usernam
