Re: 5.1.47-bin.jar behaves like STRICT_ALL_TABLES mode is in effect.
Posted by: Richard Foletta
Date: July 11, 2019 08:03AM

Thank you for your post. I did eventually add the jdbcCompliantTruncation=false to the connection string which solved my problem. I only run 1 mysqld version on each server. So it appears that the connector started to enforce this rule in version 3.1.13 according to change notes, so I did not see this behavior until moving to 5.1.47.

Again, thanks for your reply.

Options: ReplyQuote


Subject
Written By
Posted
Re: 5.1.47-bin.jar behaves like STRICT_ALL_TABLES mode is in effect.
July 11, 2019 08:03AM


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.