> yeah this is the same thing. if you get A's ID column in there > instead of C's the problem would not occur....i think this is why our > own test suite doesn't have these issues. ive made the "A->B FK > match" previous checkin recursive, so it also matches "A->C,D,E,....", > in r3759. > > >>> actually, what would prevent the issue in the first place would be >>> if you use the A_tbl.db_id column in your poly union instead of >>> B_tbl.db_id. in 0.4, mappers always use the base table's column as >>> the primary key column and it actually would not even search for >>> B_tbl.db_id. >>> >> hmm i'll check if i can do this way (as i also support 0.3.x). >> in the mean time, one more of the same... >> and how exactly to guess through the A.join(B).join(C)... that C.dbid is equivalent with A.dbid? ask mapper for equivalence? or should that be additional info given to polumunion maker and coming from inheritance chain?
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
