Why Uber Engineering Switched from Postgres to MySQL

subs

"Likewise, the birth_year index is clustered in ascending order, like this" táblában van egy hiba. :)

Lehet, hogy üzemeltetési szempontból a MySQL sokkal jobb, de nekem meg van egy listám, amin a MySQL hülyeségeit kezdtem el gyűjteni, fejlesztői szemmel:

1. The way that view queries are processed may be "unexpected" by some, and this is one reason that using "views" in MySQL can lead to performance problems, as compared to the way view queries are processed by other relational databases.
   Forrás: http://stackoverflow.com/questions/13944946/how-do-i-get-mysql-to-use-a…
2. Transactions cannot be nested. This is a consequence of the implicit commit performed for any current transaction when you issue a
   

   START TRANSACTION

   statement or one of its synonyms.
   Forrás: http://dev.mysql.com/doc/refman/5.7/en/implicit-commit.html

3. The
   

   CHECK

   clause is parsed but ignored by all storage engines.
   Forrás: http://dev.mysql.com/doc/refman/5.7/en/create-table.html

4. A stored function or trigger cannot modify a table that is already being used (for reading or writing) by the statement that invoked the function or trigger.
   Forrás: http://dev.mysql.com/doc/refman/5.7/en/stored-program-restrictions.html
5. If you specify an index type that is not valid for a given storage engine, but another index type is available that the engine can use without affecting query results, the engine uses the available type.
   Forrás: http://dev.mysql.com/doc/refman/5.7/en/create-index.html
6. You don't have
   

   FULL JOINS

   on MySQL
   Forrás: http://stackoverflow.com/questions/4796872/full-outer-join-in-mysql

7. TIMESTAMP

   has a default of 0 unless defined with the

   NULL

   attribute, in which case the default is

   NULL

   .
   Forrás: http://dev.mysql.com/doc/refman/5.7/en/timestamp-initialization.html

Kérésre bármelyik pontról szívesen írok, hogy miért probléma.