On 10 February 2010 23:33, Sayane <say...@gmail.com> wrote: > I think that an easy way to define your own user model is better idea. Auth > app should be more generic. It should define a protocol for user, group and > permission objects /../
Why should permissions and groups be in the same app as the user? Less reusable that way. Identity is different from authentication is different from authorization. Premature optimization or not, as it is today on many sites the user-table is hit extremely frequently. I'm not sure it is wise to have layer upon layer between the user in the db and the zillion things that has a foreign key to it. HM -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
