Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1W3NOS-0004Xv-4R for pgsql-docs@arkaria.postgresql.org; Wed, 15 Jan 2014 10:08:16 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1W3NOR-0003M4-G0 for pgsql-docs@arkaria.postgresql.org; Wed, 15 Jan 2014 10:08:15 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1W3NOQ-0003Lx-Nk for pgsql-docs@postgresql.org; Wed, 15 Jan 2014 10:08:14 +0000 Received: from mail-ee0-x22d.google.com ([2a00:1450:4013:c00::22d]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1W3NON-0003Ni-4J for pgsql-docs@postgresql.org; Wed, 15 Jan 2014 10:08:13 +0000 Received: by mail-ee0-f45.google.com with SMTP id b15so670030eek.32 for ; Wed, 15 Jan 2014 02:08:09 -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=RTOz+1l66vc+Igb0txbN/4LEC7r3J60uHlIfNQV24SE=; b=gJE10DuQR9NazTdjPFnRptKPN6/tErI0c6j6v6bARyuNsy7Hs/24cx0yBaLmhXm5z8 4tgmI7WwyoACjRec+ed5mazEx/xhWNfJQdkS5f1Sks5AWw+ed20MmF6qlrgdAZ8Ze9dM p8n9BMXN/oqKfYL16V/AllF5MibMZrRI2bOdqaafDk5uCyLkLUJ2PvEcW/+5cycR5z2d Ippxm3L3vql6gMJ1xrNZGQSRHHClmEHb+rlyjqlp1STGC2xdlNz3HxqePbg2Pph3o4yy hyOHmmvKs8wH3v4W9nS/Y19Bvg0Jgph4lSrrpRZIs8jZhLY3ZWpR3lnImuQbGeg/Hz+X KBew== X-Received: by 10.14.173.7 with SMTP id u7mr2424120eel.24.1389780489520; Wed, 15 Jan 2014 02:08:09 -0800 (PST) MIME-Version: 1.0 Received: by 10.14.75.198 with HTTP; Wed, 15 Jan 2014 02:07:29 -0800 (PST) In-Reply-To: <20140114202128.GA7761@momjian.us> References: <24220.1389466350@sss.pgh.pa.us> <20140111190246.GG28089@momjian.us> <24577.1389467569@sss.pgh.pa.us> <20140112042306.GM28089@momjian.us> <20140113025904.GB22464@momjian.us> <20140113140433.GA7868@momjian.us> <20140114202128.GA7761@momjian.us> From: Pavel Stehule Date: Wed, 15 Jan 2014 11:07:29 +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=047d7b62432e64cb1504efff7c46 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 --047d7b62432e64cb1504efff7c46 Content-Type: text/plain; charset=UTF-8 2014/1/14 Bruce Momjian > On Mon, Jan 13, 2014 at 03:36:18PM +0100, Pavel Stehule wrote: > > Agreed. I added a sentence in the first mention of GET DIAGNOSTICS, > and > > indicated it was generic for that command. What I also added was > your > > description of when to use := and =, but I put it in the C comments > so > > we have a record of it and if we need to expand the description or > > behavior later. > > > > > > I'll be more happy if a comment about GET DIAGNOSTICS statement will be > in user > > space. > > 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 Regards Pavel > -- > Bruce Momjian http://momjian.us > EnterpriseDB http://enterprisedb.com > > + Everyone has their own god. + > --047d7b62432e64cb1504efff7c46 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable



2014/1/14 Bruce Momjian <bruce@momjian.us>
On Mon, Jan 13, 2014 at 03:36:18PM +0100, Pavel Stehule w= rote:
> =C2=A0 =C2=A0 Agreed. =C2=A0I added a sentence in the first mention of= GET DIAGNOSTICS, and
> =C2=A0 =C2=A0 indicated it was generic for that command. =C2=A0What I = also added was your
> =C2=A0 =C2=A0 description of when to use :=3D and =3D, but I put it in= the C comments so
> =C2=A0 =C2=A0 we have a record of it and if we need to expand the desc= ription or
> =C2=A0 =C2=A0 behavior later.
>
>
> I'll be more happy if a comment about GET DIAGNOSTICS statement wi= ll be in user
> space.

I thought you would say that. =C2=A0:-) =C2=A0I don't see how thi= s 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.


:)<= br>
just notice - sorry for my English

=3D= =3DAssign=3D=3D
Using ":=3D" is preffered as assign= statement due conformity with ADA language (a plpgsql ancestor).


=3D=3DGET DIAGNOSTICS=3D=3D

Using &quo= t;=3D" is highly preferred due conformity with ANSI/SQL


Regards

Pavel


=09 =09 =09 =20 =09 =09 =09
=C2=A0
--
=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. +

--047d7b62432e64cb1504efff7c46--