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. a google search for "specified more than once" and "django" turned up very little - so I wonder if this particular error is commonly seen, or is the result of a less common situation that could be avoided somehow...perhaps my string of foreign key relationships is too long? when I tried to bash this out interactively, the interpreter gave the same error and once it had given that error subsequent work with that queryset just returned: "ProgrammingError: current transaction is aborted, commands ignored until end of transaction block" and I had to exit and start over. Thanks for any thoughts or advice. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
