Mortiz, have you taken a look at django-guardian, it has been out as long as
object level hooks have been implemented; I have been using it successfully
since version 0.2 which is about 2 years now.
Your need to add ‘object_permissions’ to a model is an incorrect approach in my
opinion as it
On Apr 16, 5:29 pm, Craig Lucas wrote:
> Ok let me know when its available. One thing I noticed in downloading that
> branch is there are no references to "db_schema" anywhere in the code. I
> wasnt sure if that branch was supposed to contain it or not.
>
> Its also
Hi,
>> Both of these were fixed by using the new implementations from Django
>> itself, and re-applying our small changes.
>>
>> Should I raise backwards-incompatibility tickets for these? They're pretty
>> obscure, and I can't imagine many people are doing them. I raised #17891
>> because the
Ok let me know when its available. One thing I noticed in downloading that
branch is there are no references to "db_schema" anywhere in the code. I
wasnt sure if that branch was supposed to contain it or not.
Its also possible that I downloaded the wrong branch. From
On Apr 16, 5:07 pm, Craig Lucas wrote:
> I would be happy to test it. I just need a little guidance on how to
> implement schemas. Like do I use db_schema in the meta class, is it in the
> settings.py file? I saw some posts about setting the SCHEMA value in the
>
I would be happy to test it. I just need a little guidance on how to
implement schemas. Like do I use db_schema in the meta class, is it in the
settings.py file? I saw some posts about setting the SCHEMA value in the
settings.py file, but not sure that would work as it seems like that would
limit
On Apr 13, 5:06 pm, Craig Lucas wrote:
> I can attempt to merge his changes in and test it. Do people typically
> merge these changes in manually? I see changes from a bunch of different
> people over the last 4 years, should I just grab the last guys changes?
The most