i think i found the culprit. i was trying this: if u replace the B-join select( [table_A, table_B.c.dataB], table_A.c.atype == 'B', from_obj= [join( table_A, table_B, table_B.c.db_id == table_A.c.db_id, )], )
with the simpler join( table_A, table_B, table_B.c.db_id == table_A.c.db_id ).select( table_A.c.atype == 'B' ) or the one with the outerjoin as of that v2366 testcase, the problem is gone/solved/not appearing in sqlite - but then postgress complains about the duplicating column. so: Similarly, because of the A-B-C-D inheritance and to avoid the duplicating columns, the C-join in this case has that complex select( ..from_obj..) instead of just join(). if u put just join() there, the thing works - for A,B,C case - as C is a leaf and does not need a select(). Adding D inheriting from C will mean that C-join would have to be again select(...fromobj...) and voila, same error. That's why i did not catch this earlier just doing A,B,C. svil --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
