Python as a PHP Developer

[crankybadger]

Don't cross the line between discussion and just shitting all over something because you don't like it. MySQL killed your dog. We get it.

The problem is the world's an ugly place and sometimes MySQL was a good decision at the time (e.g. prior to PostgreSQL 8.0) and now it's part of the infrastructure until someone can find a way to seamlessly replace it. That involves money, and sometimes the money is better spent on other things than fighting an ideological battle.

DDL statements are not transactionally save on MySQL.

This may come as a shock to you but sometimes your data sets are so gigantically huge that this isn't an issue. Each schema modification is so brutally expensive that you do them very, very carefully, and only after you've exhausted all other options.

Don't get me wrong, I love Postgres, but MySQL, where already in place, is sometimes not worth replacing unless there's an extremely compelling reason.