From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Greg Stark <stark(at)enterprisedb(dot)com> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Display of foreign keys in psql |
Date: | 2009-06-10 22:39:56 |
Message-ID: | 15710.1244673596@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greg Stark <stark(at)enterprisedb(dot)com> writes:
> On Wed, Jun 10, 2009 at 11:21 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Greg Stark <stark(at)enterprisedb(dot)com> writes:
>>> TABLE test2 CONSTRAINT test2_y_fkey FOREIGN KEY (y) REFERENCES test1(a);
>>
>> +1
> Even there the "TABLE" is kind of optional. It would stlil make sense as
> Referenced by:
> test2 CONSTRAINT test2_y_fkey FOREIGN KEY (y) REFERENCES test1(a)
I think that goes against our message style guidelines (46.3.9:
"When citing the name of an object, state what kind of object it is").
Not sure if brevity is worth a small chance of confusion.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | J. Greg Davidson | 2009-06-10 23:58:43 | 8.4beta[12] set returning function fails -- was O.K. with 8.3 |
Previous Message | Greg Stark | 2009-06-10 22:33:38 | Re: Display of foreign keys in psql |