Re: Inheritance of foregn key constraints.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrzej Mazurkiewicz <andrzej(at)mazurkiewicz(dot)org>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Inheritance of foregn key constraints.
Date: 2014-04-01 14:37:47
Message-ID: 16937.1396363067@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrzej Mazurkiewicz <andrzej(at)mazurkiewicz(dot)org> writes:
> After reading please comment if there are more objections for changing the
> depedency type for trigger to constraint dependency from the
> DEPENDENCY_INTERNAL to DEPENDENCY_AUTO.

I'm not sure which part of "no" you didn't understand, but we're not
doing that.

> lipa=> DROP TRIGGER RI_ConstraintTrigger_c_19322 ON master;
> ERROR: trigger "ri_constrainttrigger_c_19322" for table "master" does not
> exist

This has to do with case-folding and lack of double quotes, not anything
more subtle than that. A correct test would've given results like this:

regression=# drop trigger "RI_ConstraintTrigger_a_43528" on master;
ERROR: cannot drop trigger RI_ConstraintTrigger_a_43528 on table master because constraint fk0_detail on table detail requires it
HINT: You can drop constraint fk0_detail on table detail instead.

which is the behavior we need.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2014-04-01 14:45:29 pg_stat_statements cluttered with "DEALLOCATE dbdpg_p*"
Previous Message Tom Lane 2014-04-01 14:32:01 Re: WIP patch for Todo Item : Provide fallback_application_name in contrib/pgbench, oid2name, and dblink