Re: BUG #17261: FK ON UPDATE CASCADE can break referential integrity with columns of different types

From: Marcus Gartner <marcus(at)cockroachlabs(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17261: FK ON UPDATE CASCADE can break referential integrity with columns of different types
Date: 2021-11-01 22:03:50
Message-ID: CAJ2Nfu_xVpV5gZYu04scKbizOgSNVF7AEEtwo7u1S64KiZY8hg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> PG Bug reporting form <noreply(at)postgresql(dot)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
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2021-11-01 23:12:39 Re: BUG #17261: FK ON UPDATE CASCADE can break referential integrity with columns of different types
Previous Message Tom Lane 2021-11-01 21:59:49 Re: BUG #17261: FK ON UPDATE CASCADE can break referential integrity with columns of different types