Re: 5.1.47-bin.jar behaves like STRICT_ALL_TABLES mode is in effect.
Posted by: Filipe Silva
Date: July 11, 2019 04:34AM

In order to be compliant with JDBC specs, Connector/J enforces SQL_MODE=STRICT_TRANS_TABLES by default on all connections. Even if you disable it on server, the driver turns it on when creating new connections.

So, if you really want to disable STRICT_TRANS_TABLES you'll have to remove it from server's @@GLOBAL.SQL-MODE system variable and set the option jdbcCompliantTruncation=false in the connection string which tells Connector/J to skip this verification.

I'm not sure about the errors you're getting in the sql-mode setting but such option exists at least since MySQL 5.0. So chances are that you are setting some unknown value or setting it in the wrong place.

Also mind that if you have both servers running on same machine you may have to be very careful with what you put on global my.cnf file as both servers can end up reading it and not all settings are supported by all server versions.

Options: ReplyQuote

Written By
Re: 5.1.47-bin.jar behaves like STRICT_ALL_TABLES mode is in effect.
July 11, 2019 04:34AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.