Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128759
Precedence: list
MIME-Version: 1.0
References: <CANdUeaZhn-8b2+LZDV3UnT1sx+BVFcz=m7neQHyv7huGega+_Q@mail.gmail.com>
 <CE73D727-9546-469F-A723-FE667CA4061D@gmail.com> <CANdUeaZ0u-BmdUuX9XD--H2CA0zys+J8j5Cem4YQd2Q555m9Vw@mail.gmail.com>
 <CAGBsUrftu_-XfQQhKpBM_YJp_VOJJ1FyWNi+1wqZ+77q4LQSiQ@mail.gmail.com>
 <7b1f853f-1bb0-4d84-975b-164a71e092cc@allenjb.me.uk> <CAGBsUrc3-M-wZYaF0nxFgcvrGkeeMHU3geRBw+FyOwn+q1z60Q@mail.gmail.com>
In-Reply-To: <CAGBsUrc3-M-wZYaF0nxFgcvrGkeeMHU3geRBw+FyOwn+q1z60Q@mail.gmail.com>
Date: Wed, 1 Oct 2025 12:02:24 -0400
Message-ID: <CANdUeaajbj9gNj7Gr7N68xgiae8ysnL+fBBWhbxnHyx6oasgtw@mail.gmail.com>
Subject: Re: [PHP-DEV] [Discuss] Add PDO disconnect() and isConnected()
To: Kamil Tekiela <tekiela246@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000047d62f06401aff72"
From: rposky@gmail.com (Robert Wolf)

--00000000000047d62f06401aff72
Content-Type: text/plain; charset="UTF-8"

> This sounds better, but I would argue that if it's a PERSISTENT
> connection, then it should be impossible for the user to close it. The
> idea is that the connection should remain open after being established
> and should only close when the server restarts.

I think this reads too much into the "persistent" language, which does not
derive from PDO but rather PHP resources. PDO cannot guarantee a connection
always be open, nor should it be defining what connection viability is -
it's an application-level concern, and an overreach.

> What scenario would necessitate the user to close a connection that
should never close?

I provided some examples in the thread as to why a user could want to close
a connection, maybe unconvincingly.

> What I am trying to say is that there should be no need to ever close
> a persistent connection. If it ever gets messed up, it should be
> restored to the working state rather than being closed.

Thinking along these lines, what could meet this objective and satisfy some
of the concerns outlined here, would be an interface to declare the
persistent connection as defunct, such that upon subsequent PDO creation, a
new connection will be formed, and the former will be closed. This is
distinct from a disconnect or reconnect procedure, and similar to failing a
"liveness" check upon persistent PDO creation. Users could then effectively
replace their persistent PDO in the same manner they would do so for a
"regular" PDO.

Difficulties in unset($pdo) to force a disconnect are still present though
perhaps can be mitigated with the refactoring efforts outlined in "Future
Scope" to break apart the mutual PDO and PDO statement references.

--00000000000047d62f06401aff72
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">&gt; This sounds better, but I would argue that if it&#39;=
s a PERSISTENT<br>&gt; connection, then it should be impossible for the use=
r to close it. The<br>&gt; idea is that the connection should remain open a=
fter being established<br>&gt; and should only close when the server restar=
ts.<br><br>I think this reads too much into the &quot;persistent&quot; lang=
uage, which does not derive from PDO but rather PHP resources. PDO cannot g=
uarantee a connection always be open, nor should it be defining what connec=
tion viability is - it&#39;s an application-level concern, and an overreach=
.<br><br>&gt; What scenario would necessitate the user to close a connectio=
n that should never close?<br><br>I provided some examples in the thread as=
 to why a user could want to close a connection, maybe unconvincingly.<br><=
br>&gt; What I am trying to say is that there should be no need to ever clo=
se<br>&gt; a persistent connection. If it ever gets messed up, it should be=
<br>&gt; restored to the working state rather than being closed.<br><br>Thi=
nking along these lines, what could meet this objective and satisfy some of=
 the concerns outlined here, would be an interface to declare the persisten=
t connection as defunct, such that upon subsequent PDO creation, a new conn=
ection will be formed, and the former will be closed. This is distinct from=
 a disconnect or reconnect procedure, and similar to failing a &quot;livene=
ss&quot; check upon persistent PDO creation. Users could then effectively r=
eplace their persistent PDO in the same manner they would do so for a &quot=
;regular&quot; PDO.<br><br>Difficulties in unset($pdo) to force a disconnec=
t are still present though perhaps can be mitigated with the refactoring ef=
forts outlined in &quot;Future Scope&quot; to break apart the mutual PDO an=
d PDO statement references.</div>

--00000000000047d62f06401aff72--