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 and null=True at the foreign key (here: model Song). -ld On Sep 18, 6:21 pm, Tiago Serafim <tsera...@gmail.com> wrote: > 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 Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
