1回答
- 新しい順
- 投票が多い順
- コメントが多い順
0
Strict mode is OFF by default on RDS MySQL 8, we have sql_mode=NO_ENGINE_SUBSTITUTION
only. As long as you do not add any of STRICT_TRANS_TABLES
(when merged) or NO_ZERO_DATE
or NO_ZERO_IN_DATE
in your sql_mode
, it should not break your application in the future.
We recommend however to use strict mode when possible to avoid subtle data inconsistencies in the future.
回答済み 1年前
関連するコンテンツ
- 質問済み 6年前
- AWS公式更新しました 1年前
- AWS公式更新しました 2年前
- AWS公式更新しました 3年前
But when I run against the instance: "show variables like 'sql_mode'"
I get the value: "STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION"
even though in the param group only the value NO_ENGINE_SUBSTITUTION was defined
You might be looking at your session variables. Does executing these queries show differences?
If they do differ, then your client connection may be setting a custom SQL mode during connection. You will need to make sure your application does not do the same.
Thanks, indeed my JDBC client added it on session start. I solved it by setting the "jdbcCompliantTruncation" key to "false" in the driver properties.