On 03.06.21 22:49, David Christensen wrote:
> Presented for discussion is a POC for a DELETE CASCADE functionality,
> which will allow you one-shot usage of treating existing NO ACTION and
> RESTRICT FK constraints as if they were originally defined as CASCADE
> constraints. I can't tell you how many times this functionality would
> have been useful in the field, and despite the expected answer of
> "define your constraints right in the first place", this is not always
> an option, nor is the ability to change that easily (or create new
> constraints that need to revalidate against big tables) always the best
> option.
I think, if we think this is useful, the other way around would also be
useful: Override a foreign key defined as ON DELETE CASCADE to behave as
RESTRICT for a particular command.
