[sqlalchemy] Re: Vertical partitioning, mappers and foreign keys

2009-08-20 Thread Michael Bayer
not sure what the exact setup is here, but if you're trying to load from A-B across multiple tables that cross from one database to another, you'll have to roll that by hand i.e. using a plain Python method on your parent class; its not possible to do a join across two different databases

[sqlalchemy] Re: Vertical partitioning, mappers and foreign keys

2009-08-18 Thread Nathan Harmston
I m still having problems with this vertical partitioning malarky (I think the previous problem was due to a redundant copy of one of the tables existing in the wrong database) , and it seems to currently be when I have a secondary table involved between the two vertical partitions engine1 =

[sqlalchemy] Re: Vertical partitioning, mappers and foreign keys

2009-08-14 Thread Michael Bayer
Nathan Harmston wrote: HI, I m currently trying to vertical partition my database and I have split it into two groups of tables (say { documents, table1, table2 } and { table3 }. So I have s_engine = create_engine(t_database_string)#, echo=True) #echo=debug)#, echo=True) t_engine =