Re: review: psql: edit function, show function commands patch
Pavel Stehule <pavel.stehule@gmail.com>
From: Pavel Stehule <pavel.stehule@gmail.com>
To: "David E. Wheeler" <david@kineticode.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>, Jan Urbański <wulczer@wulczer.org>, Postgres - Hackers <pgsql-hackers@postgresql.org>
Date: 2010-08-09T15:30:24Z
Lists: pgsql-hackers
2010/8/9 David E. Wheeler <david@kineticode.com>: > On Aug 8, 2010, at 8:38 PM, Tom Lane wrote: > >> Um, but \sf *doesn't* give you anything that's usefully copy and >> pasteable. And if that were the goal, why doesn't it have an option to >> write to a file? >> >> But it's really the line numbers shoved in front that I'm on about here. >> I can't see *any* use for that behavior except to figure out what part of >> your function an error message with line number is referring to; and as >> I said upthread, there are better ways to be attacking that problem. >> If you've got a thousand-line function (yes, they're out there) do you >> really want to be scrolling through \sf output to find out what line 714 >> is? > > Suggestion: > > \sf without line numbers > \sf+ with line numbers it did it :) Pavel > > Best, > > David >