| From: | Rod Taylor <rbt(at)zort(dot)ca> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Greg Sabino Mullane <greg(at)turnstep(dot)com>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: psql: show which tables contraints are for with a \d |
| Date: | 2002-08-16 11:49:17 |
| Message-ID: | 1029498558.24203.27.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On Fri, 2002-08-16 at 01:15, Tom Lane wrote:
> Rod Taylor <rbt(at)zort(dot)ca> writes:
> > It should be noted that my patch in the queue displays the actual
> > foreign key definition and suppresses 'Constraint' Triggers.
>
> > This is a touch better than the below with the side effect that if a
> > user issues a CREATE CONSTRAINT TRIGGER manually it is mistakenly
> > hidden.
>
> I was thinking of looking into pg_depend to discover whether a trigger
> is associated with a constraint, and hiding the trigger if and only if
> we have a constraint to show instead. Anyone want to pursue that?
I had assumed that since the keyword CONSTRAINT isn't documented on the
CREATE TRIGGER page, that the check for isconstraint would be enough?
Erm, except legacy stuff would be hidden.
Sure, I'll fix it up.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-08-16 13:27:54 | Re: connect_timeout parameter in libpq |
| Previous Message | Ulrich Neumann | 2002-08-16 08:40:07 | Re: Antw: Re: File for /src/backend/port/netware |