On Jan 10, 4:00 pm, Josh Ourisman <[EMAIL PROTECTED]> wrote: > It's for the purpose of defining foreign keys. Basically, ClassA1 > needs to be able to reference ClassB1 and ClassB2 as foreign keys, > while ClassB3 needs to reference ClassA1 as a foreign key.
By now you know why this isn't working (models.py for neither app can be loaded by Python because of the circular references.) You could split your two models.py into multiple files. In particular, place each "cross referenced" model into its own file. That way, you will be able to import those cross referenced classes by name. See this: http://code.djangoproject.com/wiki/CookBookSplitModelsToFiles -Rajesh D --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
