From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Francisco Reyes <lists(at)natserv(dot)com> |
Cc: | pgsql General List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Named constraints |
Date: | 2002-05-23 04:02:59 |
Message-ID: | 20020522210028.T62292-100000@megazone23.bigpanda.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 22 May 2002, Francisco Reyes wrote:
> On Wed, 22 May 2002, Stephan Szabo wrote:
>
> > On Wed, 22 May 2002, Francisco Reyes wrote:
> > > GroupID integer
> > > constraint fkgroup
> > > references Groups,
> >
> > Nope, that's right, it's just that the trigger
> > names aren't the same as the constraint name.
>
> Would be nice if the triggers used more meaninful names.
I don't actually think that'd be too hard, although
the names would have to have something added to make
them more unique. Jan would probably know why the
current naming was chosen.
>
> > If you violate the constraint it should use the
> > given names, and when drop constraint works with
> > fk constraints it'll use them as well.
>
> Is there a way to list the constraints?
> I did not see any '\d' parameter to list them.
The only way I know of to get the constraint name for foreign
keys requires reading tgconstrname from pg_trigger.
From | Date | Subject | |
---|---|---|---|
Next Message | Tille, Andreas | 2002-05-23 08:00:05 | How to select rows with values set to NULL |
Previous Message | Francisco Reyes | 2002-05-23 03:41:11 | Re: Named constraints |