The user model, because the model defined by AUTH_PROFILE_MODULE is
intended to be an extension to the actual user model. Namely the
profile.
Why would you bind something to a user's profile, instead of the user
itsself? If you want to "allow records of people without Users", then
use blank=True
I`d go with the first. It`s easier to get the current logged in user and all
other pluggable apps use User, so it's a common thing to do and you can
integrate things easily .
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
I'm still making my first site with django so I don't how much weight my
opinion has, but I used a seperate profile for ForeignKeys. I don't know
why, it just seemed logical at the time. It is easer as you can refer to
whats in a users profile easier. You can put things like {{
3 matches
Mail list logo
