Hi Chris... great write up. my only thought was: why do you need multiple tables to store the row level permissions?
Luke has recently submitted a 'GenericForeignKey' in http://files.lukeplant.fastmail.fm/public/python/lp_tagging_app_0.1.zip which may be of interest. it would allow you to store all the information in a single table then. (it stores the content-type of the table as well) other questions to ponder: are you going to allow 'blanket' permissions user/group X is allowed to do Y on ALL rows? are you going to allow negativity ? ie.. person X is NOT allowed to see row Y. regards Ian On 28/05/2006, at 4:47 AM, Chris L wrote: > > Hi Ian, > > Wrote up a summary on the wiki page: > http://code.djangoproject.com/wiki/RowLevelPermissions > > Please let me know what you think, if anyone else has any input please > let me know. > > Right now, I'm working through the source code in more depth then my > previous exploration of it, and will be modifying the wiki page to > expand and modify what is written there during my journey into it. Any > mistakes you notice, please let me know. > > Thanks, > > Chris > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
