Re: remove undocumented assign syntax from plpgsql doc
От | Pavel Stehule |
---|---|
Тема | Re: remove undocumented assign syntax from plpgsql doc |
Дата | |
Msg-id | CAFj8pRCWRHFbi9FQcfHY++Yoy6s78Ph9Bs3jS_AJ2hgvvx1HLQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: remove undocumented assign syntax from plpgsql doc (Bruce Momjian <bruce@momjian.us>) |
Ответы |
Re: remove undocumented assign syntax from plpgsql doc
Re: remove undocumented assign syntax from plpgsql doc |
Список | pgsql-docs |
2014/1/15 Bruce Momjian <bruce@momjian.us>
On Wed, Jan 15, 2014 at 11:07:29AM +0100, Pavel Stehule wrote:The problem is that these are philosophical issues that are not normally
> I thought you would say that. :-) I don't see how this detail makes
> sense in the sections related to the syntax usage, so I looked in the
> section Porting from Oracle PL/SQL, and I don't see how it fits there
> either.
>
>
>
> :)
>
> just notice - sorry for my English
>
> ==Assign==
> Using ":=" is preffered as assign statement due conformity with ADA language (a
> plpgsql ancestor).
>
>
> ==GET DIAGNOSTICS==
>
> Using "=" is highly preferred due conformity with ANSI/SQL
covered in our docs. What I have done is to add a mention of which
option is compliant to the new text. Patch attached.
Is GET DIAGNOSTICS defined in the standard for SQL/PSM only or for
generic SQL?
I found this statement in ANSI SQL 92 - and few minutes searching - it is in generic SQL - today "SQL framework" part and it is enhanced in "SQL/PSM"
Regards
Pavel
Pavel
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
В списке pgsql-docs по дате отправления: