Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122313
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
In-Reply-To: <33dda53d-e4f8-42f0-a4ca-08271aba045c@app.fastmail.com>
Date: Wed, 7 Feb 2024 05:03:30 +0900
Cc: php internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <03CD1CB0-1D3D-405E-A812-5F47AED38F60@sakiot.com>
References: <1d6e1a6a-7508-40d1-a146-a7b9f67327b4@app.fastmail.com>
 <BF0589E0-D555-4CCD-B68B-253C73325933@sakiot.com>
 <33dda53d-e4f8-42f0-a4ca-08271aba045c@app.fastmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Subject: Re: [PHP-DEV] [Proposal] Add `savepoint()` method to PDO
From: saki@sakiot.com (Saki Takamachi)

> There's been discussion recently about how to deal with =
incompatibilities between different PDO drivers, especially now that we =
can have subclasses per driver.  That may be the way to deal with it.  I =
don't have a major opinion on the approach, other than all =
incompatibilities should be handled in a consistent way.

I was thinking of an implementation method like `lastInsertId()`, but =
there is certainly another way to use a subclass.

Personally, I was thinking of implementing, for example, SQL99-compliant =
(included) functions in PDO Core Class, and vendor-specific original =
functions in subclasses. However, I don't have a strong opinion on how =
they should be used, as there is still not much precedent for =
subclasses.

I agree with you that it should be a consistent implementation. I'm not =
sure if all incompatible features should be implemented in subclasses, =
or just vendor-specific features, but at least yes. There should be =
consistency.

Regards.

Saki=