SQL_MODE management it's outside of the rackables responsibility.
SQL_MODE is related to the mysql configuration, and it depends on the state
of the configuration for given mysql instance. That means it behaves
differently if you create fresh mysql instance or execute upgrade. System
admins can control if the config files should be updated during the process
Racktables as an application should just adapt to the SQL_MODE which is
shipped with default fresh mysql server installation, and there should be
note in the racktables release about that mysql change setting and how it
From what I remember SQL_MODE in newer versions of mysql are more strict,
and thus closer to official PL/SQL standard.
On Wed, Nov 7, 2018 at 1:33 AM Denis Ovsienko <denis@xxxxxxxxxxxxx> wrote:
---- On Wed, 07 Nov 2018 07:28:09 +0000 Sander Klein <roedie@xxxxxxxxx>
> I was wondering what version is the current release? Is that 0.20.14
> is the 0.21.1 release stable as well?
> Also since both release are older, will there be a new release any
0.21.x is mostly ready to become the new stable with 0.21.2, except I have
not figured it out why SQL_MODE ends up different between a freshly
installed 0.21.x and a 0.21.x upgraded from the previous release (see
https://wiki.racktables.org/index.php/NewRelease for the procedure),
that's why it had not happened earlier. Are there any MySQL masters around
to troubleshoot this discrepancy? I am sorting through too many things at