MySQL 5.7 .. also IDGen module - question (consequences?)

Implementing
1

Hello all,

when using MySQL 5.7 (because we do not have experience with downgrades on U*nx), reading in this wiki and stackoverflow, to make it run, we did some things; maybe you know about the consequence (security, compatibility with … whatever) with what we did:

a/ setting in the advance set-up the URL connection string to: default_storage_engine instead of storage_engine

b/ changing the sql-mode values: // display them: SELECT @@sql_mode

// change: for liquibase execution in general SET GLOBAL sql_mode=(SELECT REPLACE(@@sql_mode,‘ONLY_FULL_GROUP_BY’,’’));

c/ change: for the IDGen module, because the datetime default caused an error // date_created datetime NOT NULL default ‘0000-00-00 00:00:00’,

//change: SET GLOBAL sql_mode=(SELECT REPLACE(@@sql_mode,‘STRICT_TRANS_TABLES’,’’)); SET GLOBAL sql_mode=(SELECT REPLACE(@@sql_mode,‘NO_ZERO_DATE’,’’));

May we ask, if you knew, does this have an impact? Thank you

1 Like
2

Thanks @bci, it was helpful in starting IDGen. As setting them the way you told would wipe the changes after MySQL restart. So, to permanently replace those sql_modes, one must append following lines to file /etc/mysql/my.cnf:

[mysqld]
sql-mode="NO_ZERO_IN_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"

These modes are all the sql_modes shown by SELECT @@sql_mode, excluding the ones that @bci is replacing in above post. Might be helpful to someone. Thanks.

3

I’m still getting the error ‘No controller provider: coreapps’