You are creating a model yourself though. You're just saying "don't use htis model, as it was created automagickally". You can have an AnonymousUser model (class?) which already exists. You could then edit it via however you want it to edited (the db is whats important) and have permissions set to it.
On Oct 25, 10:46 am, "Dj Gilcrease" <[EMAIL PROTECTED]> wrote: > On Sat, Oct 25, 2008 at 2:59 AM, David Cramer <[EMAIL PROTECTED]> wrote: > > > I think being able to specify permissions for the AnonymousUser is > > useful, but hacking this in as a row in the database for User is not > > the right approach. > > > I'm +1 for the ability to give permissions to anonymous users. > > How would you suggest doing it then? Since creating a model that will > only ever hold one item seems kind of odd to me and in order to > specify permissions there needs to be some model to to assign the > permissions to. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
