Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: 201的特有功能,是与mysql进行比较的吗?比如全局临时表

Is the unique feature of 201 meant to be compared with MySQL? For example, global temporary tables.
Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: 201的特有功能,是与mysql进行比较的吗?比如全局临时表
Is the unique feature of 201 meant to be compared with MySQL? For example, global temporary tables.
It feels like it’s not just a comparison with MySQL, but more about reflecting TiDB’s understanding of databases and the differences from traditional databases.
It can be understood as a feature of TiDB as a distributed database.
Can global temporary tables be understood as session-level?
Relatively speaking, it should be MySQL, after all, it is compatible with the MySQL protocol.
Well, TiDB cannot be considered as having MySQL at its core. It’s just that TiDB-server is compatible with MySQL’s connection protocol. The core should be TiKV using the RocksDB setup. In fact, you can use TiKV directly without using TiDB-server.
Not only compared to MySQL, but Oracle’s temporary tables also have some similar functionalities. It should just be introducing the features of global tables.
Protocol compatibility does not mean it is MySQL. Otherwise, triggers and the like would not be directly usable.
Try to be as compatible as possible with the MySQL ecosystem, thereby reducing the learning and migration costs for DBAs.