On Tue, 2007-10-30 at 13:16 +0000, Wiley wrote: > I've run into a problem with a lookup that follows a long long chain > of foreign key relationships spanning two apps (two groups of database > tables with different app label prefixes)... > > the error is: table name > "a_long__list__of__relationships__that__eventually__gets__cut_off..." > specified more than once.
Without more concrete information, in particular the models involved and the query you are trying to do, it's hard to debug this. Try to trim down your models so that only the affected fields are involved and so that we don't have to plough through three dozen lines of code that aren't relevant. My guess would be that there's a circular relationship somewhere in your models and you are visiting the same table twice. I could believe that the current SQL construction would be fooled in that case. To debug this further, you could also put a print statement in django.db.backends.utils.CursorDebugWrapper.execute(). Print out the sql parameter just before it passes it to the database. Regards, Malcolm -- Monday is an awful way to spend 1/7th of your life. http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
