On Feb 2, 2006, at 2:13 PM, Michael Bayer wrote:
you want to set primary keys on a selectable ? selectables are supposed to very closely relate to SQL constructs. the mapper level is where you can define your not-quite-SQL constructs and how they map to your SQL constructs. since a SELECT statement in SQL doesnt have a primary key, im not sure its appropriate ?
maybe (or likely) i've misunderstood something. my basic thoughts were: 1. mappers can be used to map against arbitrary selects. 2. so i have some mapper factory functions which take any selectable as arguments. 3. i expected that i could pass in "real" tables or "abstract"/view-like selectables into my factory functions transparently. but maybe that's not the case? do my factory functions need to be more aware of whether they're getting a real table vs. an aliased selectable? thx,d ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Sqlalchemy-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
