Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121877
Return-Path: <saki@sakiot.com>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 90945 invoked from network); 30 Nov 2023 14:03:23 -0000
Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5)
  by pb1.pair.com with SMTP; 30 Nov 2023 14:03:23 -0000
Received: from php-smtp4.php.net (localhost [127.0.0.1])
	by php-smtp4.php.net (Postfix) with ESMTP id E720C18002F
	for <internals@lists.php.net>; Thu, 30 Nov 2023 06:03:30 -0800 (PST)
X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on php-smtp4.php.net
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,SPF_HELO_NONE,
	SPF_PASS autolearn=no autolearn_force=no version=4.0.0
X-Spam-Virus: No
X-Envelope-From: <saki@sakiot.com>
Received: from mail.sakiot.com (mail.sakiot.com [160.16.227.216])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
	(No client certificate requested)
	by php-smtp4.php.net (Postfix) with ESMTPS
	for <internals@lists.php.net>; Thu, 30 Nov 2023 06:03:30 -0800 (PST)
Received: from smtpclient.apple (softbank060067217005.bbtec.net [60.67.217.5])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by mail.sakiot.com (Postfix) with ESMTPSA id 8054E401E7;
	Thu, 30 Nov 2023 23:03:18 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sakiot.com;
	s=default; t=1701352998;
	bh=k1o3GDPJZSmwZqWKvchg4zfUS4YYTWonuu8G0FSfcso=;
	h=Subject:From:In-Reply-To:Date:Cc:References:To:From;
	b=bR5c8hXpIz/+/ZXG5BqqSf3UpxziuVX3Qlz4Ph8eYOjoRFo+pjeiGDN2IivUsFUav
	 KSPqK+XizPplNxubHqM63BHmNIOswZSj9eM98Nm8cQYOv1QmpynfWY7+M/y69X/a3u
	 wMakK1XatC4eSpwQYsYhSxwZ3jbRjqmtRJJZA5rs=
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
In-Reply-To: <SN1PR12MB2573419D0ACE231E4C20FB1DDB82A@SN1PR12MB2573.namprd12.prod.outlook.com>
Date: Thu, 30 Nov 2023 23:03:05 +0900
Cc: PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <A86FDD56-92FE-4FDE-B786-590F0C89136A@sakiot.com>
References: <6A2118D9-6DD0-4273-A2C0-A1088C05314D@sakiot.com>
 <SN1PR12MB2573419D0ACE231E4C20FB1DDB82A@SN1PR12MB2573.namprd12.prod.outlook.com>
To: Jeffrey Dafoe <JDafoe@fsx.com>
X-Mailer: Apple Mail (2.3731.700.6)
Subject: Re: [PHP-DEV] [PDO] 2 phase commit
From: saki@sakiot.com (Saki Takamachi)

Hi Jeff,

> Would the implementation use the underlying RDBMS two-phase commit? Or =
would the proposal be to try to build something at the PDO layer to =
mimic two-phase commits? The former seems good, the latter, not so much.

When implementing this, if each DB driver's API has a two-phase commit =
function, I would like to use it. I don't mean "emulate" it with PDO.

I haven't checked all the DB APIs because I'm still thinking about =
whether to propose it, but I've confirmed that at least Firebird's API =
has that functionality.

Regards.

Saki=