Re: [sqlalchemy] composite property not working on a mapped select

2010-12-08 Thread Will Weaver
Cool, thank you. Due to the bug I moved away from mapping a selectable to do the job. But I'll keep in mind what you've said. On Tue, Dec 7, 2010 at 9:01 PM, Michael Bayer mike...@zzzcomputing.com wrote: its a bug, and theres a new ticket http://www.sqlalchemy.org/trac/ticket/1997 with a

[sqlalchemy] composite property not working on a mapped select

2010-12-07 Thread Will
Hello, I've been trying to map two tables that have 25 columns each in addition to keys. The parent table's (descriptions) column values represent the key in a dictionary and the child table's (values) column values represent the values of the dictionary. i.e.: table 'descriptions':

Re: [sqlalchemy] composite property not working on a mapped select

2010-12-07 Thread Michael Bayer
its a bug, and theres a new ticket http://www.sqlalchemy.org/trac/ticket/1997 with a small patch. I would suggest maybe not using composites for this for now. Most of what composite does you can accomplish using descriptors: class Value(object): @property def custom_values(self):