On Fri, Jul 25, 2008 at 11:39 AM, Bram de Jong <[EMAIL PROTECTED]> wrote:
> For freesound.org I really need per-object permissions and caching.
> I would also love to use the {% cache %} template tag as much as
> possible because it's so easy and transparent!
> Now, say for example I have a sound, and a user can either edit it or
> not, or vote for it or not.AFAIK is_authenticated doesn't enter into it at all. You meant per-object permissions as in http://code.djangoproject.com/wiki/RowLevelPermissions yes? That link has got examples also. Model objects in Django are rows in a table in some SQL-capable database. Some such databases already have a system for row-level permissions but AFAIK every database does it differently... so Django is getting a portable system, see link. The question is really whether the system described in the link will be 100% tied up with the admin-system or not. I haven't tried the branch but have been using the newforms-admin branch (and need to clean up my repos), if the rowlevelpermissions-branch is run as competently as nfa was you have nothing to fear. HM --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
