Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114032
Return-Path: <tekiela246@gmail.com>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 95895 invoked from network); 12 Apr 2021 12:50:48 -0000
Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5)
  by pb1.pair.com with SMTP; 12 Apr 2021 12:50:48 -0000
Received: from php-smtp4.php.net (localhost [127.0.0.1])
	by php-smtp4.php.net (Postfix) with ESMTP id 5D32F1804DA
	for <internals@lists.php.net>; Mon, 12 Apr 2021 05:51:20 -0700 (PDT)
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT,
	FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,
	SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2
X-Spam-Virus: No
X-Envelope-From: <tekiela246@gmail.com>
Received: from mail-qv1-f50.google.com (mail-qv1-f50.google.com [209.85.219.50])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(No client certificate requested)
	by php-smtp4.php.net (Postfix) with ESMTPS
	for <internals@lists.php.net>; Mon, 12 Apr 2021 05:51:19 -0700 (PDT)
Received: by mail-qv1-f50.google.com with SMTP id j3so6137787qvs.1
        for <internals@lists.php.net>; Mon, 12 Apr 2021 05:51:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to
         :cc;
        bh=Sx34xPZmFpytBDlL6tJblwZXj3YwZ1iCn9r9+MQYvBM=;
        b=AWYgPKe3Wd14oDHicrBlrEDtr6o4Udxtok0ArGQGGd3odg7DMUJM3iMtzrhbHplpyT
         dZgGrRtUtlOViKLqUyAl8bL30B5glPZx9WTHxuouTrTvvM1RfZPzPyi20NL6aTHfyxGO
         qo7AXwnBAPT+MFrkx2xDSIaWSqKKvnqTyCZC67dV1pQ+il/09j2kt7++efPJyHjjzDOS
         5ENM8ESOYa3UwRwClHpo4Jat90oQZCsI5c8bzzyvzUlUAYWpDV7jeMEmalRpTfv+rM60
         8/Z7SDwHdplop/SlY2nI0V+5pIA3pvHZ3xElFU90wkiYSGi5SI36Jd0wG2rYyFCzOF6o
         SiIg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:cc;
        bh=Sx34xPZmFpytBDlL6tJblwZXj3YwZ1iCn9r9+MQYvBM=;
        b=osbS2BbHOhpyyNA4j68pltGtsmor27zWKD+7fQGfYcXm0t5B/w2WN+/hGUPLpv4A2G
         gir9WZT5ma58HD83eVjEsRBr/C/GjMzYGNsudYZc/8gSGlZHTRalTWHO2AZaj0K72mGG
         MLAIWF8bgclnLaT8XtSidMGdUr0mD3MM59limpeqexq+CxcslVtQzjKTuJXZZVStAuAi
         pNeZiTmqmikUTFVta0kaeQjIsqQmiKAc86S3p5duIM412Axo2+IPfIB4uoC8hd/zNydA
         FOlU6D9rspsALNAZcZE2y30HaugFiTXgsska8Cq6k/cRfPa3/lG+1mO5DOw618bEnyyg
         YpuA==
X-Gm-Message-State: AOAM531sABWsK5l0k8Pe4SgrlOYdUQfVGK46YypzmE4hPhWsMHksTPFg
	X2IQHYlQfad/+IzFiYYBFvxPXY21bSYAmonUHIMpNiAvxWw=
X-Google-Smtp-Source: ABdhPJzTsUTIDvs9f9TAg7gc5386rCqAcg3qPQwPjEJaSuoCgIVMQ5m/YR0YE1pYDt4HAoHVn7OB9+CHBOD7/BaDwvE=
X-Received: by 2002:a05:6214:2607:: with SMTP id gu7mr27018875qvb.18.1618231878429;
 Mon, 12 Apr 2021 05:51:18 -0700 (PDT)
MIME-Version: 1.0
References: <CAF+90c_PyPCd0ndtvZocJwD73_sxgxQYsOiAw8V5tSjTH3oR1A@mail.gmail.com>
 <1ffb0fbf-43f9-274a-37e0-8b650c02042b@gmail.com>
In-Reply-To: <1ffb0fbf-43f9-274a-37e0-8b650c02042b@gmail.com>
Date: Mon, 12 Apr 2021 13:51:07 +0100
Message-ID: <CAGBsUrf9pd_dBKE4LzL26nLJYa+m8eMFnQQFzoKO2Tv1ofsNXg@mail.gmail.com>
To: Dik Takken <dik.takken@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000472fed05bfc5f8dc"
Subject: Re: [PHP-DEV] Allow commit() without transaction?
From: tekiela246@gmail.com (Kamil Tekiela)

--000000000000472fed05bfc5f8dc
Content-Type: text/plain; charset="UTF-8"

What would be a benefit of a commit function that can be executed without
an active transaction?

--000000000000472fed05bfc5f8dc--