On Sat, 2007-06-30 at 14:35 -0500, Jeremy Dunck wrote:
> On 6/30/07, Dennis K. <[EMAIL PROTECTED]> wrote:
> > The magic behind ManyToManyFields relies on all models (well, the
> > models used in the relationship) being present in an appname.models
> > module. When I did that, the thing magically worked.
>
> Yeah, ORM lookups are implemented by descriptors which are added to
> related classes when they're loaded. And model classes are loaded by
> django.db.model.loading.get_models, which do expect
> appname.models.Model naming.
>
> I just think it's a bug that it's not documented. :)
There are a few tricky problems to work around when using models
(particularly relations between models) at the top-level in the same
file they are created in. Because the import of that file has not fully
completed when the code is run, the app cache isn't correctly populated.
It's sort of the ugly-cousin of #1796, but probably even harder to work
around (particularly as #1796 might have a solution now; stay tuned).
The pragmatic solution here is 'don't do that' -- fully import the files
containing model definitions with foreign relations *before* you try to
use the relations in code. Maybe there's a really tricky fix for it, but
I haven't worked out what that would be yet.
So, yeah, documentation would be consistent, but it won't stop people
trying to do this and the fix will remain the same ("don't").
Cheers,
Malcolm
--
Quantum mechanics: the dreams stuff is made of.
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
-~----------~----~----~----~------~----~------~--~---
