2007/6/20, David Larlet <[EMAIL PROTECTED]>: > 2007/6/20, Gábor Farkas <[EMAIL PROTECTED]>: > > > > David Larlet wrote: > > > 2007/6/18, David Larlet <[EMAIL PROTECTED]>: > > >> Hi, > > >> > > >> I've just tried to use the permission_required decorator for my views > > >> and I realise that there is a missing 'retrieve' permission. It's a > > >> bit odd because others ones follow the CRUD permissions. > > >> > > >> Am I missing something here? > > >> > > >> The patch is trivial: > > >> Add 'retrieve' to the auth.management._get_all_permissions function, > > >> but I don't want to hack my django code so I wonder why this choice > > >> had been done? (I suspect the admin goal which is driven by the > > >> User.is_staff field but auth can be used elsewhere). > > >> > > >> David > > >> > > > > > > Am I the only one who deal with this kind of permission issue? Or > > > maybe there is an evident solution that I haven't found yet? > > > > > > you can create your own permissions: > > > > http://www.djangoproject.com/documentation/model-api/#permissions > > > > I know this solution which require to modify all my models or, easier, > to hack the auth.management._get_all_permissions function as I said > before. > > I just wonder why this permission is not part of the default > permissions (like add, change and delete)? > > David > No more thoughts about that? I'm really surprised that it only happens to me, maybe I will be luckier on the users' mailing-list?
David --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
