From 96419dcb23729df52dbec9d2b27f3c9c24f87ed4 Mon Sep 17 00:00:00 2001 From: Tim Otten Date: Fri, 4 Dec 2020 16:35:37 -0800 Subject: [PATCH] dev/core#2188 - Upgrader - Cleanup any invalid combinations of is_search_range=1 These invalid configurations were previously asymptomatic in 5.30 but became symptomatic in 5.31. --- CRM/Upgrade/Incremental/sql/5.33.beta2.mysql.tpl | 3 +++ 1 file changed, 3 insertions(+) diff --git a/CRM/Upgrade/Incremental/sql/5.33.beta2.mysql.tpl b/CRM/Upgrade/Incremental/sql/5.33.beta2.mysql.tpl index 3acc52239d..284ac1f7f7 100644 --- a/CRM/Upgrade/Incremental/sql/5.33.beta2.mysql.tpl +++ b/CRM/Upgrade/Incremental/sql/5.33.beta2.mysql.tpl @@ -1 +1,4 @@ {* file to handle db changes in 5.33.beta2 during upgrade *} + +{* dev/core#2188, dev/core#337 (redux) - Ranges aren't support on these widgets. Note: This same change ran previously in 5.9.beta and contemporaneously in 5.32.1, and that's OK. *} +UPDATE civicrm_custom_field SET is_search_range = 0 WHERE html_type IN ('Radio', 'Select') AND data_type IN ('Money', 'Float', 'Int'); -- 2.25.1