Talk:EPrints and MySQL 8: Difference between revisions
NO_AUTO_CREATE_USER is not a valid sql_mode? |
No edit summary |
||
| Line 1: | Line 1: | ||
This setting is giving me an error in mysql8: sql_mode = NO_AUTO_CREATE_USER | This setting is giving me an error in mysql8: sql_mode = NO_AUTO_CREATE_USER | ||
I don't think this is a valid setting in either MySQL or MariaDB? | I don't think this is a valid setting in either MySQL or MariaDB? | ||
In addition, I get this warning about the other settings: | |||
'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release. | |||
Should we include the following in the sql_mode command/setting: STRICT_TRANS_TABLES ? | |||
Latest revision as of 20:06, 22 August 2023
This setting is giving me an error in mysql8: sql_mode = NO_AUTO_CREATE_USER I don't think this is a valid setting in either MySQL or MariaDB?
In addition, I get this warning about the other settings:
'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
Should we include the following in the sql_mode command/setting: STRICT_TRANS_TABLES ?