Re: [sqlalchemy] Mixed inheritance mapping and multiple binds

2010-01-19 Thread Ross Vandegrift
On Mon, Jan 18, 2010 at 07:24:45PM -0500, Michael Bayer wrote: > The argument against the tables being broken out in get_bind() is > partially one of implementation performance and partially one of > ambiguity, i.e. join of a to b, which table wins ? Neither argument > is completely compelling, th

Re: [sqlalchemy] Mixed inheritance mapping and multiple binds

2010-01-18 Thread Michael Bayer
On Jan 18, 2010, at 6:27 PM, Ross Vandegrift wrote: > > Shouldn't this work on SA 0.5.8? > > engine = create_engine('sqlite:///:memory:', echo=True) > metadata.create_all(engine) > binds = { device_table : engine, > switch_table : engine } > Currently its looking at the mapped table

[sqlalchemy] Mixed inheritance mapping and multiple binds

2010-01-18 Thread Ross Vandegrift
Hello, I've run into a case where my code works with a single engine binding but breaks if bound to multiple engines. I'm doing some things that might be considered weird - mixing joined and single table inheritance to reduce data storage, inheriting mappers from other derived mappers. The except