Ah, very interesting, exactly what I was looking for, thanks for the
tip.
Jacek
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
d
On Feb 18, 2010, at 9:29 AM, Jacek Furmankiewicz wrote:
> Is it possible to intercept the QuerySets that Django generates?
Yes, make a custom manager:
http://docs.djangoproject.com/en/dev/topics/db/managers/
Brief: When you use 'objects' (as in MyModel.objects), you're using the default
m
Is it possible to intercept the QuerySets that Django generates? Maybe
there is some generic QuerySetFactory per each entity that we could
use to filter out the disallowed instances?
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to thi
On Feb 17, 11:53 pm, Jacek Furmankiewicz wrote:
> We have a use where we need to limit access to particular *instances*
> of objects.
> It's not a simple case of add/delete/update permissions.
>
> Let's say a sales rep has his 5 customer he is responsible.
> In the customer admin he should only se
We have a use where we need to limit access to particular *instances*
of objects.
It's not a simple case of add/delete/update permissions.
Let's say a sales rep has his 5 customer he is responsible.
In the customer admin he should only see those 5 and no others.
Also, in all other admin screens (e
5 matches
Mail list logo
