On Nov 9, 2007, at 5:10 PM, [EMAIL PROTECTED] wrote:
>
>
>> yeah this is the same thing. if you get A's ID column in there
>> instead of C's the problem would not occuri think this is why our
>> own test suite doesn't have these issues. ive made the "A->B FK
>> match" previous checkin recu
> yeah this is the same thing. if you get A's ID column in there
> instead of C's the problem would not occuri 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.
yeah this is the same thing. if you get A's ID column in there
instead of C's the problem would not occuri 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.
On Nov 9
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, 20
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
