> I actually hadn't thought of that. I thought there would be one and
> only one type of checking for each model. I can't think of a use case
> for multiple checkers, but then again it's Friday and my brain is a
> little fried :)
No worries about the fried brain, I can understand that. It's been
On 7/14/06, Chris Long <[EMAIL PROTECTED]> wrote:
>
> How would you handle multiple checkers? I'm designing RLP to work on
> top of model level checking. Would it be:
I actually hadn't thought of that. I thought there would be one and
only one type of checking for each model. I can't think of a
How would you handle multiple checkers? I'm designing RLP to work on
top of model level checking. Would it be:
checker = (RowLevel, ModelLevel,)
How is the order of permissions checking done if it is multiple? Is it
the order they are specified as?
One thing that will need to be done if it is
Sorry it took so long to respond. Busy week.
On 7/8/06, Chris L <[EMAIL PROTECTED]> wrote:
>
> I've currently set up enabling row level permissions using the meta
> class, e.g. to enable row level permissions for the Mineral model you
> would have:
>
> class Mineral(models.Model):
> name = mo
> It looks okay and you are protecting with a conditional test that checks
> for the right attribute being present. What problems are you seeing?
> It's pretty easy to get into a knot in the __new__() method there, but
> from the fragment you posted you seem to have avoided the obvious
> problems
On Sun, 2006-07-09 at 05:37 +, Chris L wrote:
[...]
> Each row in the RLP(Row Level Permission) table contains:
> - The RLP id
> - The content type for the "owner" (e.g. user, group)
> - The id of the owner
> - The content type of the object
> - The id of the object
> - The permission id
> - I
No particular wish to be a PPC developer, it's more years of habit of
trying to copy down what the prof is saying without falling too far
behind. You end up losing some vowels and other unneeded letters at
points. :-) I'll change it around.
> So the idea here is that the each row in the RowLevelP
On Sat, 2006-07-08 at 16:54 +, Chris L wrote:
> Hi,
>
> I've currently set up enabling row level permissions using the meta
> class, e.g. to enable row level permissions for the Mineral model you
> would have:
>
> class Mineral(models.Model):
> name = models.CharField(maxlength=150)
>
