Re: OneToOne on users.User cause exception in admin

2006-01-05 Thread Amit Upadhyay
Hi,On 1/6/06, Dody Suria Wijaya <[EMAIL PROTECTED]> wrote: Temporary fix can be applied by passing list_select_related=TrueThis did fix the problem. Thanks a million! :-)Din't try the other permanent solution for lack of time, will try some other time and let you know. -- Amit UpadhyayBlog: http://

Re: OneToOne on users.User cause exception in admin

2006-01-05 Thread Dody Suria Wijaya
Brant Harris wrote: I'm not really sure if this is known (is there a ticket?), but I'd bet that this problem will be cleared up after the magic removal branch goes trunk. Hopefully. This likely a little bug in contrib/admin/views/main.py. - If not specified by model, row selection list by

Re: OneToOne on users.User cause exception in admin

2006-01-05 Thread Brant Harris
I'm not really sure if this is known (is there a ticket?), but I'd bet that this problem will be cleared up after the magic removal branch goes trunk. On 1/5/06, Amit Upadhyay <[EMAIL PROTECTED]> wrote: > Hi, > > There is an open bug: > http://code.djangoproject.com/ticket/930 which talks about >

OneToOne on users.User cause exception in admin

2006-01-05 Thread Amit Upadhyay
Hi,There is an open bug: http://code.djangoproject.com/ticket/930 which talks about problem with OneToOneField when used with users.User. My model is something like this: class UserDetail(meta.Model):    user = meta.OneToOneField(users.User)    telephone = meta.CharField(maxlength=15)    # we can a