From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Abhijit Menon-Sen <ams(at)oryx(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org, gavin(at)alcove(dot)com(dot)au |
Subject: | Re: [PATCH] "\ef <function>" in psql |
Date: | 2008-09-06 05:28:38 |
Message-ID: | 11443.1220678918@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I wrote:
> * the psql command seemed to have some ideas about supplying a blank
> CREATE OR REPLACE FUNCTION command for a nonexistent function, but this
> didn't actually work. In any case it seemed poorly thought out, because
> you'd really need to pay some attention to *why* the regproc/regprocedure
> lookup failed. I just ripped it out for the moment. I'm not averse to
> the concept, if you can get it implemented properly.
While I was out at dinner, the obvious solution presented itself: define
\ef with no argument as being the command that presents an empty CREATE
FUNCTION command template to fill in. This isn't any more or less
typing than where I think you were going, and it eliminates all the
ambiguity about whether you meant to type a nonexistent function name
or just mistyped.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Hunsaker | 2008-09-06 05:49:05 | Re: hash index improving v3 |
Previous Message | Tom Lane | 2008-09-06 05:20:17 | Re: [PATCH] "\ef <function>" in psql |