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.
On Nov 9, 2007, at 10:12 AM, Michael Bayer wrote: > > r3756 fixes it. > > On Nov 9, 2007, at 2:31 AM, [EMAIL PROTECTED] wrote: > >> sorry, here the case (zip) >> it uses my own polymunion() as the SA.util one cannot handle mixed >> inheritances. >>> i have a A-B-C test case where B inherits A via joined, and C >>> inherits B >>> via concrete; anbd there are links to each other, e.g. A points to >>> B. it >>> used to work before r3735. >>> >>> now query(A) gives: >>> NoSuchColumnError: "Could not locate column in row for column >>> 'A_tbl.db_id'" >>> if A->B link is not assigned, it works. >> >>> >> <t1-B_jA-C_cB.zip> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
