From: | elein <elein(at)sbcglobal(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, elein(at)varlena(dot)com |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: RI Constraint display |
Date: | 2002-12-28 23:07:11 |
Message-ID: | 200212282309.gBSN9DkD677204@pimout3-ext.prodigy.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Then this is a distinction between the trigger name and
the constraint name? The trigger name is RI_ConstraintTrigger_437278
(or some such oid). The trigger is the implementation of the constraint
so the trigger name is what I had expected to see.
Almost all of the system generated names, sequences, triggers, etc,
have constructed names. $n for constrain names seems like an anomaly.
elein
On Thursday 26 December 2002 13:45, Tom Lane wrote:
> elein <elein(at)sbcglobal(dot)net> writes:
> > Referential integrity constraints are displayed as $n.
>
> If you didn't assign a name to the constraint, that's what the generated
> names look like. Try "CONSTRAINT foo FOREIGN KEY ...".
>
> regards, tom lane
--
----------------------------------------------------------------------------------------
elein(at)varlena(dot)com Database Consulting www.varlena.com
I have always depended on the [QA] of strangers.
From | Date | Subject | |
---|---|---|---|
Next Message | Ed L. | 2002-12-29 05:13:13 | Re: 7.3.1: test select_having ... FAILED |
Previous Message | Tom Lane | 2002-12-28 21:37:11 | Re: regex from plperl |