On Apr 17, 8:07 am, Mike <mike.t...@gmail.com> wrote: > In my app I need a way to associate objects with a specific user. Users > should not have access to other users objects. I'm implementing this in my > model by setting a ForeignKey to the user that owns the object: > > owner = models.ForeignKey(User) > > Is this a bad idea?
Seems quite sensible for the use case you describe. > Can someone explain under what circumstances I would > need to use a row level permissions app? Row level permissions are useful when you have a more complex (and possibly dynamic) scheme - a common example would be a CMS with public and restricted areas, per-area admins and a validation/publication worflow. -- 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.
