Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123368
Precedence: bulk
MIME-Version: 1.0
Date: Mon, 20 May 2024 13:03:51 +0100
Message-ID: <CA+XhMqzWf5Fev==xeKnyWHqR+h7Z5se143DfEX-NW2N_AnFDPw@mail.gmail.com>
Subject: [PHP-DEV] ext/pgsql: pg_put_line deprecation proposal
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000005637810618e17f74"
From: devnexen@gmail.com (David CARLIER)

--0000000000005637810618e17f74
Content-Type: text/plain; charset="UTF-8"

I would like to know if it would be fine to deprecate pg_put_line.

Reasoning is PQPutLine is part of the obsolete list of calls for COPY
purpose
<https://www.postgresql.org/docs/current/libpq-copy.html#LIBPQ-PQPUTLINE> since
the PostgreSQL protocol 3.0 version (supported since postgresql 7.4
released about 20 years ago, see New client-to-server protocol regarding
COPY <https://www.postgresql.org/docs/7.4/release-7-4.html>).

Related PR <https://github.com/php/php-src/pull/14250>.

Cheers

--0000000000005637810618e17f74
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I would like to know if it would be fine to deprecate=C2=
=A0<a href=3D"http://pg_put_line">pg_put_line</a>.<div><br></div><div>Reaso=
ning is PQPutLine is part of <a href=3D"https://www.postgresql.org/docs/cur=
rent/libpq-copy.html#LIBPQ-PQPUTLINE">the obsolete list=C2=A0of calls for C=
OPY purpose</a>=C2=A0since the PostgreSQL protocol 3.0 version (supported s=
ince postgresql 7.4 released about 20 years ago, see=C2=A0<a href=3D"https:=
//www.postgresql.org/docs/7.4/release-7-4.html">New client-to-server protoc=
ol regarding COPY</a>).</div><div><br></div><div>Related <a href=3D"https:/=
/github.com/php/php-src/pull/14250">PR</a>.</div><div><br></div><div>Cheers=
</div></div>

--0000000000005637810618e17f74--