On Fri, 2008-04-18 at 11:02 +0100, andy baxter wrote:
[...]
> Has anyone dealt with this problem in practice, and do people have any
> thoughts about what is the best way of doing things here, from the point
> of view of keeping the code simple, and also minimising the time spent
> doing
andy baxter wrote:
> Alex Koshelev wrote:
>
>> I usually make link to User model not profile. And have no problems
>> with usage.
>>
>>
>>
> I just tried switching to this way of doing it, and have come up against
> a problem with getting the profile data into the template. If I
Alex Koshelev wrote:
> I usually make link to User model not profile. And have no problems
> with usage.
>
>
I just tried switching to this way of doing it, and have come up against
a problem with getting the profile data into the template. If I create a
list of all users in the view, then
I usually make link to User model not profile. And have no problems
with usage.
On Apr 18, 2:02 pm, andy baxter <[EMAIL PROTECTED]>
wrote:
> Hello,
>
> I have built a data model for a virtual library, which contains the
> following classes (among others):
>
> User - the built in user class from
Hello,
I have built a data model for a virtual library, which contains the
following classes (among others):
User - the built in user class from django.contrib.auth.
Member - a profile for each user, containing extra information about
each member.
Item - a book, video, or music album
5 matches
Mail list logo
