The best way to do this is to have a ForeignKey to auth.User on the top
level object of your per user data.
Thanks, that's what I ended up doing last night.
And then do the permission checking in your view functions. This can be
eased by adding custom functions to your model.
The permissions atm do not deal with anything more granular than a
class/table level.
In my case, I don't think it'll be a problem.
You might want to look back in the archives for the ACL flamewar,
http://groups.google.co.uk/group/django-developers/browse_thread/thread/7dca63383b948d7b/2a179f3917372882?q=acl&rnum=1#2a179f3917372882
I do hope to fix this in a sensible way eventually with a default model
oriented security system, with mixins providing an easy way to add crazy
things like ACL systems. But probably not for 1.0 .
Luckily, I don't think I care yet =).
Thanks. (BTW, what's the site_profile concept?)
--david
