Date: Thu, 19 Sep 2019 13:20:49 +0900
From: Michael Paquier <michael@paquier.xyz>
To: egashira.yusuke@jp.fujitsu.com, pgsql-docs@lists.postgresql.org
Subject: Re: Is it typo of connection_name?
Message-ID: <20190919042049.GE22307@paquier.xyz>
References: <156870956796.1259.11456186889345212399@wrigleys.postgresql.org>
 <20190918014914.GJ8909@paquier.xyz>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="cYtjc4pxslFTELvY"
Content-Disposition: inline
In-Reply-To: <20190918014914.GJ8909@paquier.xyz>
Precedence: bulk


--cYtjc4pxslFTELvY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Wed, Sep 18, 2019 at 10:49:14AM +0900, Michael Paquier wrote:
> Good catch.  If you look at the code (ecpg.trailer), connection_object
> refers to the name of the parameter, while connection_name refers to
> "AS connection_object" as a whole.  So it seems to me that the
> intention is to use connection_object in the synopsis of the docs.
> Any thoughts from others?

Actually, looking around we use connection_name for other commands
like EXEC SQL or DISCONNECT, so renaming connection_object to
connection_name makes the documentation more consistent.  And done.
--
Michael

--cYtjc4pxslFTELvY
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAl2DAiEACgkQnvQgOdby
QH0r4xAAjsXmpf/QiNmQDI7Hzuf6l1oyee7+Bw4yO6NaumvEOTXQOH6paekzkvDP
stfjL2ZAHbsRr4mtiQhDH2rnCayBFH7nJQkCylaocQb+XYUP+P0cXehosc1A6iwt
08cIc1BbeimMWWNad59m1mw3CLkHkvSkP7WcDhu3bI+X8ee21/yHhKBwZiiI7Axf
KED4XSWCZUbL9urD9yLqajoh1H/hvq2mVWZ1SnpEVhG9onhgF6mY72+51c66M9nB
pPU+5TYmulfVCWH5usqKqx4qnEfXjC14G2HbtzwUIlksPA8hg5lTaf0rMDVjuBma
JG1HM8nv25Vgh+75VeSITD4+nlapMr9Y7D1VtxQ2nuJdH4yAwGczydvf+nAUit/Q
Pz8AEyGJXHBYKuRUyAd5YAflzhDFa6TLvybc5khPbB21qTMfl+WtboLKTn3AtUZ3
/Ny5j9UrWdgixBKEM8pr+waax5S5R1Si9s9bJxD6FHi1egpYnW01Zvk080fcrokM
/xLKZ/Fo6wcgK30fJmoAtHtq2y46EqM+BDSahlK3+6b0Qwkbh7dkOLYQSXCMlSnk
59DsgCm2X9FC3jEu/WXE6olcrRtuQxYSzQ3Jq+YoMc4+wmUWCO9J1DgN96tFDWxr
62q3ZmYAzlZ0rt8xz4XeYy2CRAyKBC+ao5eaU9r28Wy2p+keZXk=
=cljJ
-----END PGP SIGNATURE-----

--cYtjc4pxslFTELvY--