From: | elein <elein(at)sbcglobal(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
Cc: | elein(at)varlena(dot)com, pgsql-general(at)postgresql(dot)org |
Subject: | Re: RI Constraint display |
Date: | 2002-12-31 19:11:22 |
Message-ID: | 200212311913.gBVJDh9F127116@pimout2-ext.prodigy.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
OK, got it. Thank you for the clarifications.
--elein
On Monday 30 December 2002 20:40, Tom Lane wrote:
> Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> writes:
> > On Sat, 28 Dec 2002, elein wrote:
> >> Almost all of the system generated names, sequences, triggers, etc,
> >> have constructed names. $n for constrain names seems like an anomaly.
> >
> > I think it's been that way for check constraints for a long time unless I
> > remember incorrectly.
>
> I think you remember correctly.
>
> The "$n" convention is somewhat arbitrary, but in my mind it certainly
> beats the OID-based convention we have used for RI triggers. For one
> thing, if you issue the same table declaration twice, you'll get the
> same names associated with unnamed constraints...
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
--
----------------------------------------------------------------------------------------
elein(at)varlena(dot)com Database Consulting www.varlena.com
I have always depended on the [QA] of strangers.
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Teter | 2002-12-31 19:57:34 | Re: boolean 't' 'f' vs. '1' '0' - perl question |
Previous Message | Peter Haworth | 2002-12-31 18:49:51 | Re: boolean 't' 'f' vs. '1' '0' - perl question |