TiDB also claims MySQL compatibility at the protocol level, but the amount of unsupported features is slightly demotivating: https://docs.pingcap.com/tidb/stabl

TiDB also claims MySQL compatibility at the protocol level, but the amount of unsupported features is slightly demotivating: https://docs.pingcap.com/tidb/stable/mysql-compatibility#unsupported-features https://docs.pingcap.com/tidb/stable/mysql-compatibility#uns... Here's some of what's not supported: Stored procedures and functions Triggers Events User-defined functions FOREIGN KEY constraints #18209 FULLTEXT syntax and indexes #1793 SPATIAL (also known as GIS/GEOMETRY) functions, data types and indexes #6347 Character sets other than ascii, latin1, binary, utf8, utf8mb4, and gbk. SYS schema Optimizer trace ... Not being able to use FOREIGN KEY constraints makes me distrust the viability of something like that, because in my experience DB schemas and how they're utilized without foreign key end up being dumpsterfires. Then again, at a certain scale you kind of have to look into alternative ways of how to look at working with your data, so there's that. That said, the idea of giving people something that's compatible (for the most part) with the drivers and syntax that they already utilize is an excellent one!