mirror of
https://github.com/nextcloud/documentation.git
synced 2026-01-03 02:09:45 +07:00
generate documentation from config.sample.php
This commit is contained in:
@@ -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' => [
|
||||
|
||||
Reference in New Issue
Block a user