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 > 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 as well use PhoneNumberField from > http://www.djangoproject.com/documentation/model_api/ > # but they only do US format for now, so we would just not do any > validation on it as of now. > invitation = meta.ForeignKey(InvitationCode) > > class META: admin = meta.Admin() > > def __repr__(self): return '%r, phone: %s' % (self.user, self.telephone) > but when I try to go to > http://localhost:6680/admin/trialsapp/userdetails/ I get: > OperationalError at /admin/trialsapp/userdetails/ > (1109, "Unknown table 'auth_users' in order clause") > Request Method: GET > Request URL: > http://localhost:6680/admin/trialsapp/userdetails/ > > Exception Type: OperationalError > Exception Value: (1109, "Unknown table 'auth_users' in order > clause") > Exception Location: > /usr/lib64/python2.4/site-packages/MySQLdb/connections.py > in defaulterrorhandler, line 32 > > Can someone tell me if it is a known issue, and if there is some easy > workaround to avoid it. > > TIA, > > -- > Amit Upadhyay > Blog: http://www.rootshell.be/~upadhyay > +91-9867-359-701
