Re: Alternate user fields

On Mon, Jun 20, 2011 at 5:16 PM, raj <nano.ricky@gmail.com> wrote:
> Sorry, can you give me more details. What other things would I have to
> do to make these changes? thank you.
>
> On Jun 20, 3:08 am, Kenneth Gonsalves <law...@thenilgiris.com> wrote:
>> On Mon, 2011-06-20 at 00:03 -0700, raj wrote:
>> > Ya i got that working. Just another quick question, the django auth
>> > system took care of all the login/logout pages. Now that i have a
>> > changed user class up and running, will django automatically adapt to
>> > the new class? Like, in the html, if it says {% user.is_authenticated
>> > %}, will it automatically attribute that to the new user class? Thank
>> > you.
>>
>> no
>> --
>> regards
>> KGhttp://lawgon.livejournal.com
>> Coimbatore LUG roxhttp://ilugcbe.techstud.org/
>
> --
> You received this message because you are subscribed to the Google Groups "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
>
>

I usually just write OneToOne against the User model for profiles. The
User.get_profile feels like such an anti-pattern and I think it's
going to go bye-bye sometime in the future anyways (particularly if we
get some kind of mechanism to lazy load a developer-defined User
model).

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.