Re: [sqlalchemy] Seamlessly combining data from multiple tables into a single SQLalchemy object

2015-02-12 Thread Dun Peal
Thanks, Jonathan and Simon. With its seamless query support, association_proxy looks perfect for my needs: it's just like having the extra fields on the master table, which is where I'd put them ideally if not for some pathological technical issues. I'm going to use it. Thanks, D. On

[sqlalchemy] Seamlessly combining data from multiple tables into a single SQLalchemy object

2015-02-10 Thread Dun Peal
I have a declarative base called Foo, instances of which get most of their attributes from a Foo SQL table. However, Foo also has a bar_id attribute, which is a foreign key linking to the primary key of a Bar table. Bar is really just an extension of Foo, with a few extra attributes that belong