On 08/06/18 20:05, George Anchev via Bacula-users wrote: > Today I installed 9.2.0 FD on one of the network > workstations. Trying to run an estimate for an > incremental job tells me that "Job 0" cannot find > previous Full backup, so it will estimates a full one. > > My workaround with changing the SQL_MODE didn't work > in this case. > > On Mon, 6 Aug 2018 16:37:02 -0400 Phil Stracchino > wrote: > >> ALTER TABLE Media >> MODIFY FirstWritten datetime DEFAULT NULL, >> MODIFY LastWritten datetime DEFAULT NULL, >> MODIFY LabelDate datetime DEFAULT NULL, >> MODIFY InitialWrite datetime DEFAULT NULL; > > Can anyone please confirm if that is all that is > required to get rid of all these MariaDB related > issues? Also - how safe is it? (I really know very > little about DBs).
You probably need to go through each table and change any field (except BLOB or TEXT) that is declared NOT NULL without a DEFAULT to 'DEFAULT NULL'. As for safety, it's safe. The Bacula code is pretty careful about what it writes to the DB. "NOT NULL" or "DEFAULT" clauses are basically there to enforce sane defaults if your code does something careless, and Bacula doesn't do things carelessly. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ------------------------------------------------------------------------------ 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
