Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118911 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 77596 invoked from network); 29 Oct 2022 09:48:16 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 29 Oct 2022 09:48:16 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 8D24218005C for ; Sat, 29 Oct 2022 02:48:15 -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.7 required=5.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS16276 91.121.0.0/16 X-Spam-Virus: No X-Envelope-From: Received: from mail.kd2.org (citrouille.kd2.org [91.121.181.110]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sat, 29 Oct 2022 02:48:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bohwaz.net; s=mail; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References: In-Reply-To:Message-ID:Subject:To:From:Date:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=jiPnT7SffScFO/BDVIxF97XzWNhB/nditcENwYDV6Vo=; b=WmFfFYkgTLHLZosbJO6myKc2Gq 5UNpAQnhhbP5XjChlaYKgR66OQuo/3fgZl33aUhHcr3crnkwA4vdkO4TQ2Lz5EKEWyYiF9lVS17gc A1Vd/q/iG6392x1oovjfl2RWI7IemCX+QgjPXQytizUK+wf5f+R6iLvikwaQqbHibipY=; Received: from 244.250.23.93.rev.sfr.net ([93.23.250.244] helo=platypus) by mail.kd2.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ooiRp-00C4Iq-0J for internals@lists.php.net; Sat, 29 Oct 2022 11:48:13 +0200 Date: Sat, 29 Oct 2022 11:48:05 +0200 To: internals@lists.php.net Message-ID: <20221029114805.43a87484@platypus> In-Reply-To: References: <20221024045645.00bfc0d2@platypus> <20221025141014.342851f4@platypus> <976D48A7-2F7D-474A-88BB-11E2430D7810@php.net> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Authenticated-User: bwz@bohwaz.net X-Authenticator: login X-Invalid-HELO: HELO is no FQDN (contains no dot) (See RFC2821 4.1.1.1) X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) Subject: Re: [PHP-DEV] [RFC] [Discussion] SQLite3: remove warnings, move to exceptions From: php@bohwaz.net (BohwaZ) Hi, I updated the RFC I added a second proposal where the only change would be to throw exceptions by default in 8.3 instead of 9.0: https://wiki.php.net/rfc/sqlite3_exceptions I also changed the plan for 9.0: "Calling SQLite3::enableExceptions(true) raises E_DEPRECATED, to alert that the method will get removed" As for people using enableExceptions(true) there was previously no depreciation notice, and the method would just "disappear" without any prior notice.