From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Vik Fearing <vik(at)postgresfriends(dot)org> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 19:32:38 |
Message-ID: | CAFj8pRBxFYn=dnvEAox3ck1jhY+nfpogehw-mSWT49_MXj_HRA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
st 1. 7. 2020 v 20:19 odesílatel Vik Fearing <vik(at)postgresfriends(dot)org>
napsal:
> 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.
>
What is the source of this comment? Maybe we are speaking (and thinking)
about different languages.
I thought the language of SQL functions (ANSI/SQL) is SQL/PSM.
Regards
Pavel
> (There are a few statements that are not allowed, such as COMMIT.)
> --
> Vik Fearing
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2020-07-01 19:43:26 | Re: Remove Deprecated Exclusive Backup Mode |
Previous Message | Tom Lane | 2020-07-01 19:16:22 | Re: [PATCH] fix GIN index search sometimes losing results |