Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121881
Return-Path: <saki@sakiot.com>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 13189 invoked from network); 30 Nov 2023 21:09:48 -0000
Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5)
  by pb1.pair.com with SMTP; 30 Nov 2023 21:09:48 -0000
Received: from php-smtp4.php.net (localhost [127.0.0.1])
	by php-smtp4.php.net (Postfix) with ESMTP id 2637118002F
	for <internals@lists.php.net>; Thu, 30 Nov 2023 13:09:55 -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 13:09:54 -0800 (PST)
Received: from smtpclient.apple (softbank060067217005.bbtec.net [60.67.217.5])
	(using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits))
	(No client certificate requested)
	by mail.sakiot.com (Postfix) with ESMTPSA id 18EF2401D1;
	Fri,  1 Dec 2023 06:09:42 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sakiot.com;
	s=default; t=1701378582;
	bh=Ua3EBOCPa6cwbSMVq6iWeIMAjM26h+v7e6WPRtnzT34=;
	h=From:Subject:Date:References:Cc:In-Reply-To:To:From;
	b=BaNwetbEQWW5rFMFiUhCIusdPlXyCcUV3q2eJeKVkkTctsdCpQ/SkArrNVExGqqyM
	 oR+NzL8vgBMwXWzf2h/KOj1bfZxwfpRomfouRL0t9r+HXqH1NV2my4EAxzUa0HcGb/
	 YDZPkGG2AUhqCdRwNtrcjdeE/H091FueeyEWjZ+U=
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Date: Fri, 1 Dec 2023 06:09:30 +0900
Message-ID: <241C5896-F908-4744-B18E-C3F3792FC9BB@sakiot.com>
References: <6cfba3c2-c754-422f-8031-0f6046f828ac@app.fastmail.com>
Cc: Jeffrey Dafoe <JDafoe@fsx.com>,
 php internals <internals@lists.php.net>
In-Reply-To: <6cfba3c2-c754-422f-8031-0f6046f828ac@app.fastmail.com>
To: Larry Garfield <larry@garfieldtech.com>
X-Mailer: iPhone Mail (21B91)
Subject: Re: [PHP-DEV] [PDO] 2 phase commit
From: saki@sakiot.com (Saki Takamachi)

Hi Larry,

> I have not heard of this functionality before, so I don't know how common i=
t is.  If it's only lightly supported and in different ways, perhaps this is=
 a use case for the new per-DB subclasses?

Many DBs have this functionality, so I was thinking of implementing it in th=
e same way as `beginTransaction()` and `commit()`, rather than using subclas=
ses.

SQLite may not have a two-phase commit feature. I think to make it to be an e=
rror if I use these methods in such cases. (In fact, `commit()` etc. will al=
so generate an error if it is not supported)

Regards.

Saki=