> But when you do hit it, it mostly works. Except that this is not even slightly true. See: join performance, sub-query performance, etc. > MySQL ships with referential integrity turned on - InnoDB is the default back…
There are at least ten great engineers who've left my current company at least partially because of a single toxic individual. Every one of them decided to be 'professional' to not 'burn bridges' and they did not name…
Take responsibility for what you wrote. Here are some of your words, and the obvious implications: > performance needs a very careful eye Clearly implying that performance doesn't require a careful eye on MySQL. Which…
This doesn't match my experience at all. MySQL performance is highly variable, and it's incredibly easy to write simple queries that have truly abysmal performance. Postgres on the other hand, has always tended towards…
> But when you do hit it, it mostly works. Except that this is not even slightly true. See: join performance, sub-query performance, etc. > MySQL ships with referential integrity turned on - InnoDB is the default back…
There are at least ten great engineers who've left my current company at least partially because of a single toxic individual. Every one of them decided to be 'professional' to not 'burn bridges' and they did not name…
Take responsibility for what you wrote. Here are some of your words, and the obvious implications: > performance needs a very careful eye Clearly implying that performance doesn't require a careful eye on MySQL. Which…
This doesn't match my experience at all. MySQL performance is highly variable, and it's incredibly easy to write simple queries that have truly abysmal performance. Postgres on the other hand, has always tended towards…