3 ms·

Hi! I work for PingCAP, the company behind TiDB and come from previously working on MySQL. The gap of features missing is documented here: https://www.pingcap

by morgo 8y ago

Hi! I work for PingCAP, the company behind TiDB and come from previously working on MySQL. The gap of features missing is documented here: https://www.pingcap.com/docs/sql/mysql-compatibility/ https://www.pingcap.com/docs/sql/mysql-compatibility/ I would rate compatibility as actually pretty good: all but one SQL mode is supported (which is a feat in itself), and most of the SQL functions are supported. There are some exceptions though, some which are addressable (missing functions) and some that are not (often a property of being an optimistic system). We try to be as transparent as possible on this, which might be part of the reason why you feel there is a lot missing? If you have specific examples, I would be happy to clarify. We also have a course designed for MySQL DBAs, which is designed to make the adoption easier: https://www.pingcap.com/tidb-academy https://www.pingcap.com/tidb-academy

manigandham 8y ago
Good to see the progress, I was looking at the roadmap page: https://github.com/pingcap/docs/blob/master/ROADMAP.md https://github.com/pingcap/docs/blob/master/ROADMAP.md Views and CTEs are probably the biggest missing pieces now.
- morgo 8y ago
  The technical design for views was recently completed, and I expect to see them added soon :-) Window functions & CTEs are only very recent features in MySQL 8.0 (TiDB is 5.7 compatible). None the less, they are important for HTAP workloads, and I'm looking forward to seeing them too.