install/mysql
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

my.cnf: some changes on some parameters..

Browse Source
This commit is contained in:
Christoph
2023-08-04 13:07:16 +02:00
parent 00192cc9ca
commit 21198e49e5
4 changed files with 2167 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
Example/my.cnf.HUGE.5.7
View File

@@ -63,8 +63,43 @@ socket = /tmp/mysql.sock
## -
## - To be compartible with older programming on mysql 5.6
## -
sql-mode = "ONLY_FULL_GROUP_BY,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
#sql-mode = "ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
## - sql-mode = "ONLY_FULL_GROUP_BY,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
## -
## -
## - The default on 5.7 MySQL installations was:
## -
## - sql-mode = "ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
## -
## -
## - NOTE (on 5.7 installation):
## -
## - NO_ZERO_DATE, NO_ZERO_IN_DATE and ERROR_FOR_DIVISION_BY_ZERO are deprecated, and all of them
## - are not part of strict mode, but should be used in conjunction with strict mode and are enabled
## - by default. A warning occurs if NO_ZERO_DATE or NO_ZERO_IN_DATE is enabled without also enabling
## - strict mode or vice versa. For additional discussion, see SQL Mode Changes in MySQL 5.7.
## -
## -
## - Because NO_ZERO_DATE, NO_ZERO_IN_DATE and ERROR_FOR_DIVISION_BY_ZERO are deprecated, expect it to
## - be removed in a future release of MySQL as a separate mode name and its effect included in the effects
## - of strict SQL mode.
## -
#sql-mode = "ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
sql-mode = "ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
## - Which protocols the server permits for encrypted connections. The value is a
## - comma-separated list containing one or more protocol versions. The protocols
## - that can be named for this variable depend on the SSL library used to compile
## - MySQL. Permitted protocols should be chosen such as not to leave 'holes' in the
## - list. For details, see Section 6.3.2, Encrypted Connection TLS Protocols and Ciphers.
## -
## - NOTE:
## - As of MySQL 5.7.35, the TLSv1 and TLSv1.1 connection protocols are deprecated
## - and support for them is subject to removal in a future version of MySQL. See
## - Deprecated TLS Protocols.
## -
tls_version=TLSv1.2,TLSv1.3
## - secure-file-priv
## -
@@ -97,6 +132,7 @@ sql-mode = "ONLY_FULL_GROUP_BY,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO
## - this option.
## -
#secure-file-priv = ""
secure-file-priv = ""
## - local-infile

42
Example/my.cnf.HUGE.8.0
View File

@@ -59,11 +59,46 @@ socket = /tmp/mysql.sock
## - sql_mode
## -
## - Since Version 8.0.11 NO_AUTO_CREATE_USER is no longer available
## - Since Version 8.0.11 NO_AUTO_CREATE_USER is no longer available. The default on 8.0 MySQL
## - installations is
## -
## - For now, we will use the default value, it seems to be ok.
## - sql-mode = "ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION"
## -
#sql-mode = "ONLY_FULL_GROUP_BY,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
## - For now, we will use the default value, without deprecated NO_ZERO_IN_DATE, NO_ZERO_DATE
## - and ERROR_FOR_DIVISION_BY_ZERO (see below) - It seems to be ok.
## -
## -
## - The default on 5.7 MySQL installations was:
## -
## - sql-mode = "ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
## -
## -
## - NOTE (on 5.7 installation):
## -
## - NO_ZERO_DATE, NO_ZERO_IN_DATE and ERROR_FOR_DIVISION_BY_ZERO are deprecated, and all of them
## - are not part of strict mode, but should be used in conjunction with strict mode and are enabled
## - by default. A warning occurs if NO_ZERO_DATE or NO_ZERO_IN_DATE is enabled without also enabling
## - strict mode or vice versa. For additional discussion, see SQL Mode Changes in MySQL 5.7.
## -
## -
## - Because NO_ZERO_DATE, NO_ZERO_IN_DATE and ERROR_FOR_DIVISION_BY_ZERO are deprecated, expect it to
## - be removed in a future release of MySQL as a separate mode name and its effect included in the effects
## - of strict SQL mode.
## -
sql-mode = "ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION"
## - Which protocols the server permits for encrypted connections. The value is a
## - comma-separated list containing one or more protocol versions. The protocols
## - that can be named for this variable depend on the SSL library used to compile
## - MySQL. Permitted protocols should be chosen such as not to leave 'holes' in the
## - list. For details, see Section 6.3.2, Encrypted Connection TLS Protocols and Ciphers.
## -
## - NOTE:
## - As of MySQL 5.7.35, the TLSv1 and TLSv1.1 connection protocols are deprecated
## - and support for them is subject to removal in a future version of MySQL. See
## - Deprecated TLS Protocols.
## -
tls_version=TLSv1.2,TLSv1.3
## - secure-file-priv
## -
@@ -96,6 +131,7 @@ socket = /tmp/mysql.sock
## - this option.
## -
#secure-file-priv = ""
secure-file-priv = ""
## - local-infile

1044
Example/my.cnf.HUGE.MariaDB-10.5 Normal file
View File

File diff suppressed because it is too large Load Diff

1046
Example/my.cnf.VERY-HUGE.MariaDB-10.5 Normal file
View File

File diff suppressed because it is too large Load Diff