MySQL is going to integrate some code from Google customizations. That is extremely good and healthy, however I came across a paragraph that made me wonder if MySQL will ever stop being insane at times…
Oracle having acquired the vendor of MySQL main data storage subsystem (InnoDB), the company decided to write a new one called Falcon. This is a safe move as it could potentially threaten MySQL if Oracle decided not to play nice anymore regarding InnoDB.
However… read this:
Falcon will do crash recovery and roll-back operations faster than InnoDB because they are done from main memory, Schumacher said, but some InnoDB features, like foreign key support and full-text indexing, won’t be supported until MySQL 6.1.
Come on! How can you pretend making an enterprise-grade RDBMS and not support foreign keys? Just remember that MySQL only started to support them in version 5… I think I’ll never understand why MySQL is so bitchy about foreign keys while any other RDBMS just provides it (PostgreSQL, Firebird or Derby just do it right).
If you don’t have basic referential integrity, then please don’t call it a RDBMS: just call it a “table-based database” with SQL support.
Entries (RSS)