On Fri, Oct 10, 2008 at 09:10:50PM -0400, Tom Lane wrote:
Joshua Tolley [EMAIL PROTECTED] writes:
The new \ef psql command creates nicely usable CREATE OR REPLACE
FUNCTION ... text based on the function I tell it to edit, but the
text it creates *doesn't* include a final semicolon, so when
The new \ef psql command creates nicely usable CREATE OR REPLACE
FUNCTION ... text based on the function I tell it to edit, but the
text it creates *doesn't* include a final semicolon, so when I exit my
editor-of-choice after messing with my function, it doesn't run the
code I've given it until I
Joshua Tolley [EMAIL PROTECTED] writes:
The new \ef psql command creates nicely usable CREATE OR REPLACE
FUNCTION ... text based on the function I tell it to edit, but the
text it creates *doesn't* include a final semicolon, so when I exit my
editor-of-choice after messing with my function, it
On Fri, Oct 10, 2008 at 7:10 PM, Tom Lane [EMAIL PROTECTED] wrote:
Joshua Tolley [EMAIL PROTECTED] writes:
The new \ef psql command creates nicely usable CREATE OR REPLACE
FUNCTION ... text based on the function I tell it to edit, but the
text it creates *doesn't* include a final semicolon, so
On Oct 10, 2008, at 20:27, Joshua Tolley wrote:
Now, if you want to fix psql so that even with a semicolon there it
will redisplay the command buffer and wait for a return, then I'd
agree
that that's an improvement. I couldn't figure out how to get
readline
to cooperate with that ... but
