2010/3/21 Craig Ringer <cr...@postnewspapers.com.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 > 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. I understanding. But this functionality is implemented yet. My motivation is to design some tool for more easy searching n. row in source code (for interpretation error messages) and possibility to see this row in some context. maybe we can gently select an behave with last char in command \df+ standard output - numbered source code \dfd - show only source code (\ Detail Function Dump ) Regards Pavel > > -- > Craig Ringer > -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
