#1796: [patch] "Cannot resolve keyword ___ into field" error when working with
ManyToMany relation
------------------------------+---------------------------------------------
Reporter: anonymous | Owner: adrian
Type: defect | Status: new
Priority: high | Milestone:
Component: Database wrapper | Version: SVN
Severity: critical | Resolution:
Keywords: |
------------------------------+---------------------------------------------
Comment (by [EMAIL PROTECTED]):
Simon: Thanks. Agreed. BTW, Simon, Luke: Thanks for the quick following
ups.
I just noticed something interesting in that get_models() was importing
the model into a different module (and apparently the correct one).
For e.g. I '''''was''''' doing from 'mytest.models import *' from the
shell. However, get_models() was importing it into 'mysite.mytest.models'.
Trying 'from mysite.mytest.models import *' from the shell caused
everything to work correctly.
So could this be more of a problem with the way django sets the sys.path
than an import problem?
--
Ticket URL: <http://code.djangoproject.com/ticket/1796>
Django <http://code.djangoproject.org/>
The web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates
-~----------~----~----~----~------~----~------~--~---
