Re: proposal: more practical view on function's source code

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: more practical view on function's source code
Date: 2010-03-21 14:39:35
Message-ID: 4BA62FA7.5080204@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 21/03/2010 10:33 PM, Pavel Stehule wrote:
> 2010/3/21 Craig Ringer<craig(at)postnewspapers(dot)com(dot)au>:
>> 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.
>
> there is \ef statement now

... which I completely missed. My apologies; that problem is already solved.

--
Craig Ringer

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2010-03-21 14:52:08 Re: proposal: more practical view on function's source code
Previous Message Pavel Stehule 2010-03-21 14:33:55 Re: proposal: more practical view on function's source code