Hi Chris, The implementation detailed on the wiki appears to give the granularity that several people around here (including myself) have been looking for, minus the various points that have already been brought up. An ACL-type solution as opposed to UNIX-style permissions certainly seems more flexible. My concern is that there's no details suggesting precisely how to implement one of the more common scenarios: when you want to specify that users can only have certain permissions for rows they've created themselves. An example of this would be your forum - apart from moderators, you only want users to be able to edit their own posts.
Clearly, with the given proposal, it would be possible (and necessary) to create a new permission row for each data row the user generates. This is not especially hard, but a straightforward generic mechanism for doing this would be nice (which is to say, a mechanism that allows the admin system to generate the appropriate permissions when a user creates a new row). There might be one or two other similar situations the want considering, but this is my personal bugber at the moment. Anyway, looking good. -Andy PS: would Luke's GenericForeignKey allow for inline editing, assuming it was to be adopted? Personally I'd much rather be able to alter a row's permissions on its own admin page than have to switch table. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
