Re: [sqlalchemy] Re: Unmapped Column Error

2011-03-04 Thread Michael Bayer
just an FYI its often easier to just use the actual objects in the primary/secondary join instead of the strings. the string thing is just so that order of declaration is not an issue. On Mar 3, 2011, at 8:39 PM, Doug wrote: Thanks for the tip Michael, that solved my problem! It now looks

[sqlalchemy] Re: Unmapped Column Error

2011-03-03 Thread Doug
Thanks for the tip Michael, that solved my problem! It now looks like: category_association = Table('BankCategoryMap', Base.metadata, Column(ParentCategoryID, Integer, ForeignKey('BankCategories.ID'), primary_key=True),