Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128756
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>
In-Reply-To: <CANdUeaZ0u-BmdUuX9XD--H2CA0zys+J8j5Cem4YQd2Q555m9Vw@mail.gmail.com>
Date: Wed, 1 Oct 2025 14:55:16 +0100
Message-ID: <CAGBsUrftu_-XfQQhKpBM_YJp_VOJJ1FyWNi+1wqZ+77q4LQSiQ@mail.gmail.com>
Subject: Re: [PHP-DEV] [Discuss] Add PDO disconnect() and isConnected()
To: Robert Wolf <rposky@gmail.com>
Cc: Claude Pache <claude.pache@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
From: tekiela246@gmail.com (Kamil Tekiela)

On Wed, 1 Oct 2025 at 14:45, Robert Wolf <rposky@gmail.com> wrote:
>
> > I generally agree that there's little value to a disconnect() action; unset($pdo) is already sufficient.
>
> See the point again about persistent connections. The user has no means to disconnect in that case.
>
> > I recommend to use a name that deters users from using it in normal operations, e.g. pdo->debug_manual_disconnect().
>
> Considering the above as well, a possible stance to take could be to introduce it as persistent_disconnect(). We could then decide whether it should function on "regular" connections as well.

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. What scenario would
necessitate the user to close a connection that should never close?