On Sat, Mar 17, 2012 at 20:38, Aymeric Augustin <[email protected]> wrote: >[...] > Besides, I find project-wide "user profiles" impractical for most purposes. I > prefer subclassing auth.User even if I just need a few extra fields, and add > enough glue (middleware, auth backend, login and logout views) to hold the > pieces together.
In my latest project there's a situation where neither is useful. We have a Person model (name, address, phone, FK company etc.), and that person may or may not (yet!) have a User account. Person gets a nullable FK from User and we have to listen to post_save() on both of them to synchronize first_name/last_name/email. Would be awesome if such a use case was covered. Cheers, Danny -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
