As MySQL 5.6 now enables the SQL Mode STRICT_TRANS_TABLES for new installations, I have been running into users who have been upgrading from previous versions, and not quite sure how to test their application for compatibility with this new default.
For some applications converting warnings to errors presents an unknown-unknown, in that the operators of the system can not easily detect what may break. Certainly many deployments will have QA environments, but there is always some fear production queries are just a little bit different.
Since sql_mode is configurable on a per-session basis, there are some strategies that I have been recommending to ease transition:
- Whitelist: Have all new application components enable strict mode by default. For example, if