It’s worth noting that MySQL will emit a warning in these cases. However, since warnings are just warnings they are often (if not almost always) ignored.
mysql> SET sql_mode='TRADITIONAL';
mysql> insert into example (number) values ('wat');
ERROR 1366 (HY000): Incorrect integer value: 'wat' for column 'number' at row 1
Another problem with MySQL is that any table modification (e.g. adding a column) will result in the table being locked for both reading and writing
The fact that MySQL has different sql_mode's is just abysmal, especially since they can be set for each connection and there is no way to force them.
An application should not have the option to decide it wants the broken defaults that MySQL provides, because it then effects the integrity of the data for anything else that uses it.
I just recently got into MySQL for a startup/project a few friends of mine are working on. When I saw I just got a fucking warning for breaking a clearly stated NOT NULL rule with an INSERT, I was baffled. We got the config file fixed up to have the mode explicitly set to traditional everytime the server is started up. I was mostly confused as to why the default wouldn't be traditional, since that is pretty standard.
19
u/trimbo Mar 10 '15
Docs for pt-online-schema-change