Bug #23371 | Automatic append of STRICT_TRANS_TABLES to the sql_mode. | ||
---|---|---|---|
Submitted: | 17 Oct 2006 14:01 | Modified: | 17 Oct 2006 15:55 |
Reporter: | Sébastien Ayotte | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | Connector / J | Severity: | S3 (Non-critical) |
Version: | 5.0.3 | OS: | Linux (Linux) |
Assigned to: | CPU Architecture: | Any |
[17 Oct 2006 14:01]
Sébastien Ayotte
[17 Oct 2006 14:36]
Mark Matthews
Sébastien, The driver needs the STRICT_TRANS_TABLES mode enabled to enforce JDBC compliance on truncation checks. If you can't use STRICT_TRANS_TABLES as part of your sql_mode, then you'll have to disable truncation checks by adding "jdbcCompliantTruncation=false" as a URL configuration parameter.
[17 Oct 2006 15:55]
Sébastien Ayotte
Thanks Mark, I was going throught the doc and couldn't find the rigth options to set to disable the feature. I had old code to maintain and I need a not to strict mode for the SQL. Thanks for the quick reply :-)
[12 Apr 2024 12:00]
MySQL Verification Team
Bug #114615 marked as duplicate of this one.