From 428ab59b4b26f5d4dbaae847f2a06ed9763ee77b Mon Sep 17 00:00:00 2001 From: Nextcloud bot Date: Fri, 10 Sep 2021 04:18:42 +0000 Subject: [PATCH] generate documentation from config.sample.php --- .../config_sample_php_parameters.rst | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/admin_manual/configuration_server/config_sample_php_parameters.rst b/admin_manual/configuration_server/config_sample_php_parameters.rst index 594f0970d..493fcfaac 100644 --- a/admin_manual/configuration_server/config_sample_php_parameters.rst +++ b/admin_manual/configuration_server/config_sample_php_parameters.rst @@ -1756,6 +1756,25 @@ https://mariadb.com/kb/en/mariadb/xtradbinnodb-server-system-variables/#innodb_l http://www.tocker.ca/2013/10/31/benchmarking-innodb-page-compression-performance.html http://mechanics.flite.com/blog/2014/07/29/using-innodb-large-prefix-to-avoid-error-1071/ +:: + + 'mysql.collation' => null, + +For search queries in the database, a default collation – depending on the +character set – is chosen. In some cases a different behaviour is desired, +for instances when a accent sensitive search is desired. + +MariaDB and MySQL have an overlap in available collations, but also +incompatible ones, also depending on the version of the database server. + +This option allows to override the automatic choice. Example: + +'mysql.collation' => 'utf8mb4_0900_as_ci', + +This setting has no effect on setup or creating tables. In those cases +always utf8[mb4]_bin is being used. This setting is only taken into +consideration in SQL queries that utilize LIKE comparison operators. + :: 'supportedDatabases' => [