B
boo
re: topic - yeah, i know!
and it _does_ exist in that table!!! so why does this thing keep throwing
an exception?
i don't know the direct answer, but i know the indirect answer: because my
child table uses a composite PK! if i try this exact scenario using a
dataset where the child table's primary key is simple, everything works as
expected.
i'm not sure if it makes a difference that the FK field is also a member of
the composite PK
anyway, i am about to go hack this into shape via workaround: abolish
composite keys in child tables and replace with a surrogate simple key (ie -
an autonumber field, since the identities created by my previously defined
composite key are about to go out the window...)
....but i stopped in to wonder: has anyone else seen this behaviour? is it
a bug, or 'other'?
and it _does_ exist in that table!!! so why does this thing keep throwing
an exception?
i don't know the direct answer, but i know the indirect answer: because my
child table uses a composite PK! if i try this exact scenario using a
dataset where the child table's primary key is simple, everything works as
expected.
i'm not sure if it makes a difference that the FK field is also a member of
the composite PK
anyway, i am about to go hack this into shape via workaround: abolish
composite keys in child tables and replace with a surrogate simple key (ie -
an autonumber field, since the identities created by my previously defined
composite key are about to go out the window...)
....but i stopped in to wonder: has anyone else seen this behaviour? is it
a bug, or 'other'?