Michael Bayer wrote: >> Is it possible to specify that an ActiveMapper-derived class >> should autoload its columns but to override some of those columns >> (for example, to set a primary key that wasn't defined in the >> database)? My attempts so haven't found any hybrid between fully >> automatic and fully manual. > > this would be exactly the use case for a separate Table and Mapper > definition, and is the entire reason SA takes the approach that it > does. your tables are not your classes !
Nope, you can't do that. This use case definitely isn't one that the ActiveMapper extension is designed to handle. Listen to Mike, and move over to full-fledged SQLAlchemy. -- Jonathan LaCour http://cleverdevil.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
