| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | "Steve White" <swhite(at)aip(dot)de>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Feature request: include script file into function body |
| Date: | 2011-02-01 19:08:44 |
| Message-ID: | 590.1296587324@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> It seems to me that something which let you pull the body of a
> script file into the statement on the *client* side of the
> connection, before sending the CREATE FUNCTION statement to the
> server would not only be a lot more secure (you could only read
> files that the OS would let your login read anyway), but would be
> more *useful*.
The usual procedure is to put the whole CREATE FUNCTION statement
into a file, which you can then send with \i. I'm not quite seeing
the point of having just the body in a file? It's not like the body
is typically useful to run as standalone code.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve White | 2011-02-01 19:09:27 | Re: Feature request: include script file into function body (better syntax) |
| Previous Message | Gary Doades | 2011-02-01 18:55:20 | Re: Feature request: include script file into function body |