| From: | Vik Fearing <vik(at)postgresfriends(dot)org> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SQL-standard function body |
| Date: | 2020-07-01 18:19:25 |
| Message-ID: | ad9572f7-45d7-0095-3fa7-93cb4d70114b@postgresfriends.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 7/1/20 3:36 PM, Robert Haas wrote:
> I actually don't have a very clear idea of what the standard has to
> say about SQL-language functions. Does it just say it's a list of
> statements, or does it involve variables and control-flow constructs
> and stuff like that, too?
It's either a single sql statement, or a collection of them between
"begin atomic" and "end". There are no variables or flow control
constructs or anything like that, just as there are no such things
outside of a function.
(There are a few statements that are not allowed, such as COMMIT.)
--
Vik Fearing
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2020-07-01 18:34:33 | Re: POC: postgres_fdw insert batching |
| Previous Message | Tom Lane | 2020-07-01 18:06:05 | Re: proposal - plpgsql - FOR over unbound cursor |