From ce46834b938eb687152a680669ada95a26304178 Mon Sep 17 00:00:00 2001 From: wxiaoguang Date: Wed, 21 Jun 2023 18:49:25 +0800 Subject: Remove "CHARSET" config option for MySQL, always use "utf8mb4" (#25413) In modern days, there is no reason to make users set "charset" anymore. Close #25378 ## :warning: BREAKING The key `[database].CHARSET` was removed completely as every newer (>10years) MySQL database supports `utf8mb4` already. There is a (deliberately) undocumented new fallback option if anyone still needs to use it, but we don't recommend using it as it simply causes problems. --- custom/conf/app.example.ini | 3 --- 1 file changed, 3 deletions(-) (limited to 'custom') diff --git a/custom/conf/app.example.ini b/custom/conf/app.example.ini index e51f055883..13820095ae 100644 --- a/custom/conf/app.example.ini +++ b/custom/conf/app.example.ini @@ -344,9 +344,6 @@ NAME = gitea USER = root ;PASSWD = ;Use PASSWD = `your password` for quoting if you use special characters in the password. ;SSL_MODE = false ; either "false" (default), "true", or "skip-verify" -;CHARSET = utf8mb4 ;either "utf8" or "utf8mb4", default is "utf8mb4". -;; -;; NOTICE: for "utf8mb4" you must use MySQL InnoDB > 5.6. Gitea is unable to check this. ;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; -- cgit v1.2.3