Simon Willison wrote:
> 2. Finely grained permissions (others have mentioned this) - the
> ability to restrict which users and/or groups can modify individual
> content items, i.e. database rows.
I added my thoughts on how to implement fine grained permissions here:
http://groups.google.com/grou
Jason Huggins wrote:
> Here's how the above use-cases would be defined in my table:
Sorry, I didn't realize the formatting of my sample table only loooks
good with a fixed-width font.
> check_permissions(principal=request.user,
> permission='add_timesheet',
> user_id='jasonh')
>
> The ab
Robert Wittams wrote:
> It seems that custom authorization is a common pattern that the generic
> views and admin interface do not handle.
I agree.
> Any thoughts? I'm currently doing the first option with a wrapper round
> the generic views. But I think this should be built in.
First off, I a
Simon Willison wrote:
>
> Here are two things I would love to see added to Django:
>
> 1. Auto-versioning. I want to be able to turn this on in a model
> (auto_versioning = True or similar) and have Django automatically
> handle the gnarly details of keeping old versions of database rows
> ar
Here are two things I would love to see added to Django:
1. Auto-versioning. I want to be able to turn this on in a model
(auto_versioning = True or similar) and have Django automatically
handle the gnarly details of keeping old versions of database rows
around and the interface for rollin
