OSNews

In response to Steven Haryanto: the examples you give can be caught in application code. One thing I have learned through experience is to never trust a backend product to cleanly enforce its limits. Storing bad data (as you say MySQL does) is worse than storing nothing at all while returning an error, so in my view MySQL must change but not for the reasons you state.

It is the responsibility of the developer who creates an application that makes use of MySQL to properly handle errors and validate inputs before they go into any sort of storage. It's not that much extra work to do proper range checking in languages like PHP.