the latest trunk uses deferred mapper compilation and solves this problem (ticket #194 in trac: http://www.sqlalchemy.org/trac/ticket/ 194 )
On Jun 13, 2006, at 5:44 PM, Randall Smith wrote: > I've got 200+ tables with lots of relationships that I'm trying to map > SQLAlchemy to. I'm writing a code generator to create the classes, > mappings, etc. A problem that I don't see a simple solution to is > writing the mapper code in the proper order. If I attempt to map one > class to another that doesn't have its mapper defined yet, I get an > error. Can someone think of a fairly simple approach to writing > out the > mapper definitions in an order that meets dependencies? > > Randall > > > > _______________________________________________ > Sqlalchemy-users mailing list > Sqlalchemy-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
