Possible Duplicate:
Django: Why create a OneToOne to UserProfile instead of subclassing auth.User?
Why subclassing auth.User is not the recommended way for additional information about Users (auth.User), but creating a UserProfile?
Possible Duplicate:
Django: Why create a OneToOne to UserProfile instead of subclassing auth.User?
Why subclassing auth.User is not the recommended way for additional information about Users (auth.User), but creating a UserProfile?
I think it's not such a big difference to the recommended django way as subclass of a model will internally also be connected through a OneToOneField
to the parent class!