Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120700
Feedback-ID: i8414410d:Fastmail
User-Agent: Cyrus-JMAP/3.9.0-alpha0-499-gf27bbf33e2-fm-20230619.001-gf27bbf33
Mime-Version: 1.0
Message-ID: <85c4cba3-93f0-48c7-a78a-e936df0c59c8@app.fastmail.com>
In-Reply-To: 
 <CA+kxMuTccYGT7fH+8u7N+iZtFzd3yZviu+1_+Afs01YvE5YvQg@mail.gmail.com>
References: 
 <CA+kxMuTccYGT7fH+8u7N+iZtFzd3yZviu+1_+Afs01YvE5YvQg@mail.gmail.com>
Date: Tue, 27 Jun 2023 15:24:34 +0000
To: "php internals" <internals@lists.php.net>
Content-Type: text/plain
Subject: Re: [PHP-DEV] PDO Subclasses coming to vote soon.
From: larry@garfieldtech.com ("Larry Garfield")

On Tue, Jun 27, 2023, at 1:49 PM, Dan Ackroyd wrote:
> Hi everyone,
>
> Just giving an update on the
> https://wiki.php.net/rfc/pdo_driver_specific_subclasses RFC as time is
> running out. The RFC text has been updated with the implemented
> subclasses stubs.

The RFC doesn't specify if `new PDO(...)` changes behavior at all.  Currently, as I understand it, `$db = new PDO($postgresConnectString)` returns a PDO instance that has the Postgres-specific methods enabled, which they can use.  With this RFC, if someone does the same, will they now get back `PdoPgsql`, or will PDO still have the postgres methods, or will their code break?

--Larry Garfield