Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123236
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Mime-Version: 1.0 (1.0)
Subject: Re: [PHP-DEV] PDO subclass names
Date: Tue, 30 Apr 2024 21:41:58 +0900
Message-ID: <BDC66EAB-F9C8-4F7A-85B3-C2680DEEB17C@sakiot.com>
References: <CAL0xaBHXSTWXemYHDCzDK90K_oQFHKeZ1ojtNXJ4MEdrvgOeaA@mail.gmail.com>
Cc: Matteo Beccati <php@beccati.com>, internals@lists.php.net
In-Reply-To: <CAL0xaBHXSTWXemYHDCzDK90K_oQFHKeZ1ojtNXJ4MEdrvgOeaA@mail.gmail.com>
To: Arvids Godjuks <arvids.godjuks@gmail.com>
From: saki@sakiot.com (Saki Takamachi)

Hi Arv=C4=ABds,

>  I wasn't proposing rolling a separate driver or anything like that, just a=
n alias that would reserve a namespace for MariaDB and if there's ever a nee=
d to actually roll the driver, that alias be replaced with actual driver.
> The thing is at this point MySQL and MariaDB have a different set of addit=
ional capabilities that are not compatible between the two. Doctrine, at thi=
s point, actually makes a distinction between MariaDB and MySQL - those are c=
onsidered different databases.
> This would allow people to use MariaDB and MySQL-specific functionality by=
 using the respective driver namespace and remove any confusion about if thi=
s works with both or only one of them.
>=20
> I know it seems to be out of scope, but this deals with PDO subclass names=
 and this seems to be a thing to consider here. Sure, we can have a separate=
 RFC about it, but I think this is the right moment to handle this question.=


It's a very interesting subject, but off-topic for this thread. The purpose o=
f this thread is to make a correction based on the Namespace RFC, since the R=
FC regarding namespaces and the RFC regarding PDO subclasses are in conflict=
 with each other.

That is, the PDO subclass RFC was passed in violation of the namespace RFC, a=
nd we are proposing the appropriate fix for it.
(However, this is a very grey area. The Namespaces RFC "recommends" the use o=
f namespaces, rather than mandating it.)

Personally, I believe this fix does not require a new RFC.

Regards,

Saki=