2021-04-26, 12:50 PM
(This post was last modified: 2021-04-27, 12:34 AM by HLFadmin. Edited 2 times in total.)
Installling on a test forum. Clean 1.8.26 install, no other plugins.
Error upon activation.
I will diagnose later, other fish frying.
Database is utf8mb4. I think I just need to change the table creation specs.
STRICT_TRANS_TABLES enabled.
https://sql-info.de/mysql/notes/gotchas/...value.html
Yikes, still more after disabling STRICT_TRANS_TABLES.
Current value for sql_mode on test forum.
mysql> SHOW GLOBAL VARIABLES LIKE 'sql_mode';
+---------------+-----------------------------------------------------------------------------------------------------------------------+
| Variable_name | Value |
+---------------+-----------------------------------------------------------------------------------------------------------------------+
| sql_mode | ONLY_FULL_GROUP_BY,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION |
+---------------+-----------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)
Production forum has same, plus STRICT_TRANS_TABLES, and able to run 1.8.26 with minimum plugins, without known problems.
So, asking a general question: If I knock back some of the default sql_mode settings in order to make a plugin work, is this creating a potential for a database problem down the line?
I think my answer to continue evaluating the plugin is to drop some of the settings. But determine if improvements need to be made before going to production.
Error upon activation.
I will diagnose later, other fish frying.
Database is utf8mb4. I think I just need to change the table creation specs.
STRICT_TRANS_TABLES enabled.
https://sql-info.de/mysql/notes/gotchas/...value.html
Yikes, still more after disabling STRICT_TRANS_TABLES.
Current value for sql_mode on test forum.
mysql> SHOW GLOBAL VARIABLES LIKE 'sql_mode';
+---------------+-----------------------------------------------------------------------------------------------------------------------+
| Variable_name | Value |
+---------------+-----------------------------------------------------------------------------------------------------------------------+
| sql_mode | ONLY_FULL_GROUP_BY,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION |
+---------------+-----------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)
Production forum has same, plus STRICT_TRANS_TABLES, and able to run 1.8.26 with minimum plugins, without known problems.
So, asking a general question: If I knock back some of the default sql_mode settings in order to make a plugin work, is this creating a potential for a database problem down the line?
I think my answer to continue evaluating the plugin is to drop some of the settings. But determine if improvements need to be made before going to production.