Re: BUG #17261: FK ON UPDATE CASCADE can break referential integrity with columns of different types - Mailing list pgsql-bugs

From Marcus Gartner
Subject Re: BUG #17261: FK ON UPDATE CASCADE can break referential integrity with columns of different types
Date
Msg-id CAJ2Nfu_xVpV5gZYu04scKbizOgSNVF7AEEtwo7u1S64KiZY8hg@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17261: FK ON UPDATE CASCADE can break referential integrity with columns of different types  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #17261: FK ON UPDATE CASCADE can break referential integrity with columns of different types
List pgsql-bugs
I agree with you there. So why is an FK relationship between columns of different types even allowed?

On Mon, Nov 1, 2021 at 5:59 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
PG Bug reporting form <noreply@postgresql.org> writes:
> It is possible to break foreign key referential integrity when the FK
> columns have different types and updates are cascaded from the parent
> relation to the child relation.

I'm not really sure what you'd consider such an FK relationship to mean.
I can't get too excited about it when there doesn't seem to be a well
defined semantics for it.

                        regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #17261: FK ON UPDATE CASCADE can break referential integrity with columns of different types
Next
From: Alvaro Herrera
Date:
Subject: Re: BUG #17261: FK ON UPDATE CASCADE can break referential integrity with columns of different types