From: Ian B. <ia...@co...> - 2003-04-29 20:42:11
|
On Tue, 2003-04-29 at 12:05, Luke Opperman wrote: > Automatically creating the joins might conceivably solve this, > although I'm pretty sure I can come up with with the same import > circular dependencies whether it is at module import time (solved by > strings) or object instantiation time (although classRegistry can > probably be used to save this: you'll never import that FK'ed class > if it's already in the classRegistry...) Hmm. I think this should be okay, so long as *somebody* imports all the classes. You can't use one class until the other class has been setup (because of the fixup step). The the module that uses one class doesn't need to import all of them -- so long as they all get imported when the application gets started up (at least, that's how it should work). Ian |