Re: Template Tag - Using Sessions versus Direct DB access - pros and cons

2006-10-27 Thread Don Arbow
On Oct 27, 2006, at 9:45 AM, Merric Mercer wrote: > > Many thanks Don. I figured it out, but because of issues with google > have had problems posting back. > > It turns out that I don't even have to use get_profile. Something > like > {{ user.userprofile.postcode }} works fine, where userprof

Re: Re: Template Tag - Using Sessions versus Direct DB access - pros and cons

2006-10-27 Thread Jay Parlar
On 10/27/06, Merric Mercer <[EMAIL PROTECTED]> wrote: > > Many thanks Don. I figured it out, but because of issues with google > have had problems posting back. > > It turns out that I don't even have to use get_profile. Something like > {{ user.userprofile.postcode }} works fine, where userprof

Re: Template Tag - Using Sessions versus Direct DB access - pros and cons

2006-10-27 Thread Merric Mercer
Many thanks Don. I figured it out, but because of issues with google have had problems posting back. It turns out that I don't even have to use get_profile. Something like {{ user.userprofile.postcode }} works fine, where userprofile is the name of the one-to-one class. MerMer > On Oct 26

Re: Template Tag - Using Sessions versus Direct DB access - pros and cons

2006-10-27 Thread Don Arbow
On Oct 26, 2006, at 6:12 AM, MerMer wrote: > 1) I am able to add fields from the User class directly to a > template. > e.g. {{ user.email }}. However, I can't see a way to add the extra > fields from the UserProfile class directly to the template, even > though > it has a one-to-one relation

Template Tag - Using Sessions versus Direct DB access - pros and cons

2006-10-27 Thread MerMer
I need an authenticated user to be able to see some of their personal details on each page of the site. I have so far created a UserProfile class (which has a one to one relationship with the User class) in order to provide more information on the user. 1) I am able to add fields from the Use