Hi Brendan,
I thought you were referring to the spaces sourrounding the word "FOREIGN KEY" on the last line and hence my explaination was out of place.
I am glad that you have corrected the indentation to 4 spaces. Those were unintentional at 2 spaces from myside.
However,Why does the word "FOREIGN KEY" appear in the last line of your output. My original patch had the output like this.
Referenced by:
"bar_foo_fkey" IN public.bar(foo) REFERENCES foo(a)
The keyword "FOREIGN KEY" was removed by me as it would further cause a confusion.
Secondly, since the table foo is altered with an addition of a new column "bar", it doesn't display in your output. Please double check.
My output is looking like this:
testdb=# \d foo
Table "public.foo"
Column | Type | Modifiers
--------+---------+-----------
a | integer | not null
bar | integer | not null /* Brendan--this line is missing in your output */
Indexes:
"foo_pkey" PRIMARY KEY, btree (a)
Foreign-key constraints:
"foo_bar_fkey" FOREIGN KEY (bar) REFERENCES bar(a)
Referenced by:
"bar_foo_fkey" IN public.bar(foo) REFERENCES foo(a)
/* please ignore the 2 space indent, I am still using my orignal patch. I will correct it later */
Thanks,
Kenneth
> Date: Mon, 14 Apr 2008 11:04:35 -0400
> From: alvherre@commandprompt.com
> To: direvus@gmail.com
> CC: tgl@sss.pgh.pa.us; kd_souza@hotmail.com; pgsql-patches@postgresql.org
> Subject: Re: [PATCHES] Reference by output in : \d <table_name>
>
> Brendan Jurd escribió:
>
> > Yeah, that's what I figured. The patch I attached to my previous
> > email should fix it up.
>
> Applied, thanks.
>
> --
> Alvaro Herrera http://www.CommandPrompt.com/
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Coolhotmail : Board of the same old Email ID’s? Get a unique one here.
Try it now!