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
Not off the top of my head. The reason I made this comment is because
I like going through the timeline and having been noticing a lot of
tickets (which I thought were good features/fixes), but were marked as
wontfix by adrian with no explaination and no dialoging before hand
either.
--~--~
On Sat, 2006-07-08 at 21:37 -0700, bradford wrote:
> There are many tickets out there marked as wontfix. It would be nice
> to see an explaination of why the ticket was marked as wontfix on all
> tickets marked as wontfix.
>
> Just a brief description would do.
Most of them are so annotated, in
I never understood why you filter an object with foo=foo.id and you
create an object with foo=foo. Consistency is nice!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this gro
There are many tickets out there marked as wontfix. It would be nice
to see an explaination of why the ticket was marked as wontfix on all
tickets marked as wontfix.
Just a brief description would do.
--~--~-~--~~~---~--~~
You received this message because you a
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)
>
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)
hardness = models.PositiveSmallIntegerField()
class Admin:
Gary Wilson wrote:
> This really should be added to the model api documentation too.
db api rather.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to dj
On 7/8/06, Ian Holsman <[EMAIL PROTECTED]> wrote:
>
> nope.. it never did.
> I just use the RSS feed instead.
>
That will work for me as well. Thanks for the pointer, Ian.
Cheers,
deryck
--
Deryck Hodgehttp://www.devurandom.org/
Samba Teamhttp:/
nope.. it never did.
I just use the RSS feed instead.
On 08/07/2006, at 6:38 AM, Deryck Hodge wrote:
>
> On 6/19/06, Ian Holsman <[EMAIL PROTECTED]> wrote:
>>
>> hi.
>> I just noticed that the last email I got from django-updates was on
>> june 12.
>> has something been turned off ?
>
> Did this
11 matches
Mail list logo
