foreign key defs 390/v6 vs. 390/v7

[robert]

it seems that it was allowed to define a foreign key to
a 4 character CHAR from an INTEGER under v6.

we have some ddl (SPUFI) which works ok on our v6.1 but
dies at a client running v7. error is -538.

nothing on this ng or APARS that i could find. seems odd.

robert

[Mark A]

"robert" <gn*****@rcn.com> wrote in message
news:da**************************@posting.google.c om...

it seems that it was allowed to define a foreign key to
a 4 character CHAR from an INTEGER under v6.

we have some ddl (SPUFI) which works ok on our v6.1 but
dies at a client running v7. error is -538.

nothing on this ng or APARS that i could find. seems odd.

robert

That sounds like a bug that was fixed, and not a problem with version 7.

BTW, if your foreign key is integer and the primary key on the parent table
is char(4) (or other way around, not sure what you mean), then your DBA or
database designer should be shot (but tortured first).

[robert]

"Mark A" <[e-mail]> wrote in message news:<%3*****************@news.uswest.net>...

"robert" <gn*****@rcn.com> wrote in message
news:da**************************@posting.google.c om...

it seems that it was allowed to define a foreign key to
a 4 character CHAR from an INTEGER under v6.

we have some ddl (SPUFI) which works ok on our v6.1 but
dies at a client running v7. error is -538.

nothing on this ng or APARS that i could find. seems odd.

robert

That sounds like a bug that was fixed, and not a problem with version 7.

BTW, if your foreign key is integer and the primary key on the parent table
is char(4) (or other way around, not sure what you mean), then your DBA or
database designer should be shot (but tortured first).

yeah, i view it as a v6 bug. i was told "don't know why it doesn't work,
we ran the SPUFI just fine". love that word, SPUFI. but when your life
revolves around REDEFINES, and DB2 (pretty obviously) is coercing a 32 bit
thingee into another 32 bit thingee while your not looking; life is bliss.
i don't think they'd feel the thumbscrews <G>

[Mark A]

> > That sounds like a bug that was fixed, and not a problem with version 7.

BTW, if your foreign key is integer and the primary key on the parent table is char(4) (or other way around, not sure what you mean), then your DBA or database designer should be shot (but tortured first).

yeah, i view it as a v6 bug. i was told "don't know why it doesn't work,
we ran the SPUFI just fine". love that word, SPUFI. but when your life
revolves around REDEFINES, and DB2 (pretty obviously) is coercing a 32 bit
thingee into another 32 bit thingee while your not looking; life is bliss.
i don't think they'd feel the thumbscrews <G>

SPUFI - SQL Processing Using File Input.