From: | Greg Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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:33:38 |
Message-ID: | 4136ffa0906101533m10a1ddffh8d27aa4ad7289a51@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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:
>> So perhaps something like:
>
>> Referenced by:
>> TABLE test2 CONSTRAINT test2_y_fkey FOREIGN KEY (y) REFERENCES test1(a);
>
> +1
>
> ... although making it *really* copy-and-pastable would require a bit
> more attention to detail than I bet it's gotten. (Schema qualification
> and double-quoting-at-need being the likely trouble spots.) Still,
> we can fix that later if we have the basic appearance being compatible
> with that goal.
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)
and even like that it looks like it's the widest line in the printout
--
Gregory Stark
http://mit.edu/~gsstark/resume.pdf
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-06-10 22:39:56 | Re: Display of foreign keys in psql |
Previous Message | Mark Kirkwood | 2009-06-10 22:33:32 | Re: [HACKERS] Cursor with hold emits the same row more than once across commits in 8.3.7 |