Okay, on the one system that I upgraded to 9.0.3 I also upgraded the
database engine to mariadb 12.2.8. Was still getting the error. I then
went back to the July email and saw that they removed the
STRICT_TRANS_TABLES
<https://dev.mysql.com/doc/refman/5.7/en/sql-mode.html#sqlmode_strict_trans_tables>
from the sql_modes. I remove this and yes it does work now.
What will this affect on the whole of Bacula though? Will this cause
problems down the road?
thanks,
Jerry
Now on to the other system, half way to a weekend :)
On Fri, Sep 1, 2017 at 5:15 PM, Phil Stracchino <ph...@caerllewys.net>
wrote:
> On 09/01/17 19:10, Jerry Lowry wrote:
> >
> > I am running 5.6.28 on one of my updated servers. Once I updated the
> > bacula database and got it all running. I tried to start a job and it
> > failed with this error. Do you know if it is 5.6 or 5.6.x where the
> > problem started? There are no sql_modes for date specified any where in
> > the configuration.
>
> Jerry, I *thought* it was 5.7 but my memory could be in error.
>
> If in doubt, check what the global SQL_MODE is *in your running DB*. If
> you haven't got it set explicitly in your configuration, you're running
> on the compiled-in default.
>
>
> --
> 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
