Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121908
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Date: Sun, 3 Dec 2023 21:39:55 +0900
Message-ID: <ADC02246-85E6-4B16-972E-1EE7B7108843@sakiot.com>
References: <CAON3zHDkgV3aQ6r4mEkbdm-wAPPTa_FB6TsNeYYkF5ppJBnO9w@mail.gmail.com>
Cc: Eugene Sidelnyk <zsidelnik@gmail.com>, Deleu <deleugyn@gmail.com>,
 Bruce Weirdan <weirdan@gmail.com>, php internals <internals@lists.php.net>
In-Reply-To: <CAON3zHDkgV3aQ6r4mEkbdm-wAPPTa_FB6TsNeYYkF5ppJBnO9w@mail.gmail.com>
To: Kentaro Takeda <takeda@youmind.jp>
Subject: Re: [PHP-DEV] [PDO] 2 phase commit
From: saki@sakiot.com (Saki Takamachi)

Hi,

> Do you have any ideas how to handle this case at the core level in the
> regard of php lifecycle?

I agree with Kentaro on this. This can be said to be a weakness of two-phase=
 commit itself, but I think it should be addressed in userland or user opera=
tions.

BTW, I said that I was thinking of implementing two-phase commit in pdo core=
, but that may be a bit unreasonable. Perhaps because it is not standardized=
 in standard SQL, the method of implementing this function varies from datab=
ase to database. The steps leading up to the final commit vary greatly depen=
ding on the DB.

Looking at the current implementation for each DB, it is possible to forcefu=
lly create a method in the core, but this will break down when the DB specif=
ications change in the future.

Perhaps two-phase commit is a feature that should be implemented in pdo subc=
lasses with "retaining the personality of the DB''.

Regards.

Saki=