Tim,
I think that if you replace the term "namespace" with "group," we can do what
we both want with the same solution. Or, in other words, we're kind of saying
the same thing but using different words.
In my scenario, each user would be in one or more groups. Each user could read
or write any
That looks like a pretty good starting point. It's a little different
in that for my scenario, UserA and UserB would both be accessing
django admin, but would get different results based on what Namespaces
they have access to.
Seems like it should be pretty easy to create a Model Admin that
overwr
This is something we've been thinking a lot about recently. The direction we
are considering is something like this:
http://github.com/paltman/django-logicaldelete
This code, "logical delete," overrides the delete() method of models so that
they are simply marked as deleted, and not returned in
3 matches
Mail list logo
