Hi Chris, I have a little feedback if you are interested. [Just so you know, I'm a "heavy user" of Django but have yet to make a substancial contribution to the project]
In general I think your proposal is fine but I have a few points: -Lots of tables there! Can you acheive the same without the extra tables? I would guess you can come pretty close. I think by narrowing your functionality to *only* deal with the example you provided you can greatly simplify your implementation and the management of the db. -(Somewhat contrary to the suggestion above!) An alternative approach for the group-level changes: a new permission type that allows you to assign a group that can access that object. i.e. permissionA = access for every user in groupA. Then every user that belongs to groupA can access objects created by any user in groupA. You would then, obviously, add the permission to groupA only -How do you deal with those permissions in the generic and admin views? You may need to change the returned lists to show only those things that the user has created? I'm not sure. I know it would be an issue in the admin pages but the generic lists might be used in various ways (and perhaps the option to choose would be nice). Anyway, that's just what came to me when I was looking. Thanks for taking this on! -rob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
