Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118037 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 21464 invoked from network); 21 Jun 2022 12:50:31 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 21 Jun 2022 12:50:31 -0000 To: internals@lists.php.net Date: Tue, 21 Jun 2022 09:39:48 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 Content-Language: en-US References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 96.61.105.82 Subject: Re: [RFC] [Under Discussion] PDO driver specific sub-classes From: ramsey@php.net (Ben Ramsey) Message-ID: On 6/20/22 18:01, Dan Ackroyd wrote: > Hi, > > Following previous discussions, here is an RFC to have DB specific > classes for PDO. > > https://wiki.php.net/rfc/pdo_driver_specific_subclasses > > cheers > Dan > Ack Is there a reason we shouldn't go ahead and add subclasses for all database connection types, even if they won't have new methods added to them? For example, if I create a connection to MySQL with PDO::connect, I would get back a PDOMysql instance, and so forth. -- Cheers, Ben