On Fri, Jul 29, 2016 at 5:28 PM, Jim Nasby <jim.na...@bluetreble.com> wrote: > > The way I sum up MySQL vs PG for people that ask is to recount how they > "fixed" the Feb. 31st bug when they released strict mode (something that > they actually called out in the release PR). With strict mode enabled, Feb. > 30th and 31st would give you an error. Feb 35th was still silently > converted to March whatever. *That was the MySQL mentality: data quality > doesn't matter compared to "ease of use".* > > They've done this throughout their history... when presented with a hard > problem, they skip around it or plaster over it, and then they promote that > their solution is the only right way to solve the problem. (Their docs > actually used to say that anything other that table-level locking was a bad > idea.)
This is exactly what I mean saying MySQL speaks different language than I know, and that's why I simply cannot use it: (mysql 5.7.12) mysql> select cast('2016-99-99' as date); +----------------------------+ | cast('2016-99-99' as date) | +----------------------------+ | NULL | +----------------------------+ 1 row in set, 1 warning (0.00 sec) In Postgres: test=# select cast('2016-99-99' as date); ERROR: date/time field value out of range: "2016-99-99" LINE 1: select cast('2016-99-99' as date); ^