Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1W3TVm-0003fX-Q7 for pgsql-docs@arkaria.postgresql.org; Wed, 15 Jan 2014 16:40:15 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1W3TVm-000469-9C for pgsql-docs@arkaria.postgresql.org; Wed, 15 Jan 2014 16:40:14 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1W3TVl-000459-Kq for pgsql-docs@postgresql.org; Wed, 15 Jan 2014 16:40:13 +0000 Received: from mail-ea0-x22e.google.com ([2a00:1450:4013:c01::22e]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1W3TVe-0008Qg-GB for pgsql-docs@postgresql.org; Wed, 15 Jan 2014 16:40:13 +0000 Received: by mail-ea0-f174.google.com with SMTP id b10so595328eae.19 for ; Wed, 15 Jan 2014 08:40:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=g0yhauQn4TPkurulYzPtiM1xIzylf0f/Im0If977upI=; b=sKryifEcM/WsKBnjUFpofMFnomMQpy/oHIg3REoi8egvsazilOtZv3Viu3FQOyLJvb XXDx5P5I0/K8sL299j9X9a0U3dkGhl3heE/YVMYTOCSIi4AikFRINHP5uabQRHzfdTNJ ARsRG1h9Egvey5OvZVIPOzIuvXgtvrEwa9+dg+xMN+90xRuW2Wa9kHAcAzI5Y9vVAvqe d2hNEmUoZA3uqDVSjguGVSOHcpSEw0Qz2IKEmf0iCdeoZbrs3ShgDgPeqEM1RvSpTbmF Pk2JajU6vaxjk9yYiAq05Mb6rCJTIOHWvH37w+YDip0LiJyx/LEO+7EtaeGMvd3Itxr+ tIBw== X-Received: by 10.15.75.68 with SMTP id k44mr4978199eey.57.1389804002500; Wed, 15 Jan 2014 08:40:02 -0800 (PST) MIME-Version: 1.0 Received: by 10.14.75.198 with HTTP; Wed, 15 Jan 2014 08:39:22 -0800 (PST) In-Reply-To: <20140115163259.GA12704@momjian.us> References: <20140112042306.GM28089@momjian.us> <20140113025904.GB22464@momjian.us> <20140113140433.GA7868@momjian.us> <20140114202128.GA7761@momjian.us> <20140115153535.GA7607@momjian.us> <20140115163259.GA12704@momjian.us> From: Pavel Stehule Date: Wed, 15 Jan 2014 17:39:22 +0100 Message-ID: Subject: Re: remove undocumented assign syntax from plpgsql doc To: Bruce Momjian Cc: Tom Lane , pgsql-docs Content-Type: multipart/alternative; boundary=001a11c26ca0e0641a04f004f5f1 X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org --001a11c26ca0e0641a04f004f5f1 Content-Type: text/plain; charset=UTF-8 2014/1/15 Bruce Momjian > On Wed, Jan 15, 2014 at 04:55:11PM +0100, Pavel Stehule wrote: > > The problem is that these are philosophical issues that are not > normally > > 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" > > OK, patch updated. > ok I don't understand last sentence of comment ! /* ! * Ada-based PL/SQL uses := for assignment and variable defaults, while ! * the SQL standard uses equals for these cases and for GET ! * DIAGNOSTICS, so we support both. FOR and OPEN only support :=. ! */ ! assign_operator : '=' "FOR and OPEN only support :=" FOR statement nor OPEN statement doesn't use ":=" Regards Pavel > -- > Bruce Momjian http://momjian.us > EnterpriseDB http://enterprisedb.com > > + Everyone has their own god. + > --001a11c26ca0e0641a04f004f5f1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable



2014/1/15 Bruce Momjian <bruce@momjian.us>
On Wed, Jan 15, 2014 at 04:55:11PM +0100, Pavel Stehule w= rote:
> =C2=A0 =C2=A0 The problem is that these are philosophical issues that = are not normally
> =C2=A0 =C2=A0 covered in our docs. =C2=A0What I have done is to add a = mention of which
> =C2=A0 =C2=A0 option is compliant to the new text. =C2=A0Patch attache= d.
>
> =C2=A0 =C2=A0 Is GET DIAGNOSTICS defined in the standard for SQL/PSM o= nly or for
> =C2=A0 =C2=A0 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"

OK, patch updated.

ok

I don't understand last sentence of comment

=C2=A0! /*
!=C2=A0 * Ada-based PL/SQL uses :=3D for assignment and variable defaul= ts, while
!=C2=A0 * the SQL standard uses equals for these cases and for GET
!=C2=A0 * DIAGNOSTICS, so we support both.=C2=A0 FOR and OPEN only supp= ort :=3D.
!=C2=A0 */
! assign_operator=C2=A0=C2=A0=C2=A0 : '=3D'

"FOR an= d OPEN only support :=3D"

FOR statement nor OPEN st= atement doesn't use ":=3D"

Regards

P= avel


--
=C2=A0 Bruce Momjian =C2=A0<bruce@mo= mjian.us> =C2=A0 =C2=A0 =C2=A0 =C2=A0http://momjian.us
=C2=A0 EnterpriseDB =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 http://enterprisedb.com

=C2=A0 + Everyone has their own god. +

--001a11c26ca0e0641a04f004f5f1--