From 5fd5f3398b665540ed77893b792e7372f8087f2f Mon Sep 17 00:00:00 2001 From: Pavel Volkov Date: Mon, 13 Mar 2023 10:46:16 +0100 Subject: databases/sqlite3: reenable the DQS option Due to various ports not being prepared for this change (see 20230227 entry), the DQS option of databases/sqlite3 has been reenabled as a stop gap measure. It is scheduled to be disabled again for good no earlier than 20240101, giving downstream software authors more time to fix their queries. PR: 270064 Fixes: 47912ce2e613211aecf6ecdfc58681b7aca0df33 See also: PR 269889, 269966, 269950 --- UPDATING | 12 ++++++++++++ 1 file changed, 12 insertions(+) (limited to 'UPDATING') diff --git a/UPDATING b/UPDATING index 6d648be11f16..2def2788a33b 100644 --- a/UPDATING +++ b/UPDATING @@ -5,6 +5,18 @@ they are unavoidable. You should get into the habit of checking this file for changes each time you update your ports collection, before attempting any port upgrades. +20230313: + AFFECTS: users of databases/sqlite3 + AUTHOR: fuz@FreeBSD.org + + Due to various ports not being prepared for this change (see 20230227 + entry), the DQS option of databases/sqlite3 has been reenabled as a + stop gap measure. It is scheduled to be disabled again for good no + earlier than 20240101, giving downstream software authors more time + to fix their queries. + + See also: https://sqlite.org/quirks.html#dblquote + 20230311: AFFECTS: users of net/dshell AUTHOR: nobutaka@FreeBSD.org -- cgit v1.2.3