From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: more practical view on function's source code |
Date: | 2010-03-21 18:00:31 |
Message-ID: | 4BA65EBF.3020808@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Craig Ringer wrote:
> On 21/03/2010 8:03 PM, Pavel Stehule wrote:
>> Hello
>>
>> Current form of function detail isn't too practical (see screenshot 1)
>>
>> we can move source code to separate area (maybe we can add rownumbers)
>>
>> see screenshot 2 (it is only mockup, real implementation can be more
>> inteligent in rows numbering)
>
> Ideally, the output of the source listing could be used as input to
> CREATE OR REPLACE FUNCTION without excessive massaging. Those line
> number prefixes make it hard to grab the output of \df+ and do
> something useful with it. Sure, vim's column-edit takes care of them
> quickly enough, but it's still a pain, and if the output format is to
> be changed it might be nice to see it change in a way that makes it
> easier to re-use that source listing.
You can get there sorta by doing "\pset format unaligned" followed by
"\df+ funcname"
But I agree it's annoying to have to do two commands.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-03-21 18:08:57 | Re: proposal: more practical view on function's source code |
Previous Message | Dimitri Fontaine | 2010-03-21 17:51:52 | Re: proposal: more practical view on function's source code |