On Sunday 2018-03-18 11:41:14 Phil Stracchino wrote: > As Josip alreadp pointed out, the issue here is not the Bacula update, > it is the MariaDB update. While MariaDB is diverging from MySQL, > MariaDB 10.2 does follow the stricter SQL compliance of MySQL 5.7.
The same goes for Percona MySQL server. Probably starting with the version of 5.7 > So, as Josip explained, you need to remove NO_ZERO_DATE and > NO_ZERO_IN_DATE from SQL_MODE. However, you should be able to safely > use the following: > > sql_mode = NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION,STRICT_ALL_TABLES Yes, it is safe for bacula. What I suggested was the default setting before the 5.7 change. -- Josip Deanovic ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
