> Cutting and pasting your code into a clean project directory with the > same Django code revision as yours, this all works for me. So, as you > suspect, the problem is not with your code as written. > > Can you try the same experiment: start a new app and cut and paste the > code as written here. Then run syncdb, etc. Just to check there is > nothing weird about your current code files. > > >> 783 raise >> 784 else: # No match found. >> --> 785 raise TypeError, "Cannot resolve keyword '%s' into >> field" % name >> 786 >> 787 # Check to see if an intermediate join is required between >> current_table >> >> TypeError: Cannot resolve keyword 'article' into field >> > > This is confusing, because it would indicate that the internal model > representation is somehow out of whack. This is all being done by > looking through Python lists, etc, that were created when the class was > instantiated. There's no database activity or anything going on. > > I'm really at a loss to explain this. Will be most interested to see if > a cut-and-paste duplication can repeat the error for you. > > Malcolm > I created a brand new app from scratch (including a new MYSQL database) copied just my models.py file over, typed the code and got the same result!
I even tried the suggestion of clearing out all of the old .pyc files and I still get the same error. This is weird. The admin interface works just fine so I'm a little unclear what's going on here. Any other thoughts? Thanks, Chris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
