How Do Chinese Databases Compare in Compatibility? A Detailed Survey

1. Overview of Domestic Database Compatibility

Based on a comparison table, the article examines the compatibility of various Chinese database products with mainstream databases such as Oracle, MySQL and PostgreSQL, highlighting significant gaps among domestic solutions.

1) Compatibility Targets

Most products aim to be compatible with Oracle, MySQL and PostgreSQL; some also support DB2, SQL Server, etc. Certain products allow selection of a compatibility mode at initialization, marked as MultiDB.

2) Compatibility Levels

Kernel‑level : Compatibility built into the core engine, often derived from open‑source bases.

Product‑level : Separate products are offered to provide compatibility for a specific source database.

Database‑level : Compatibility is fixed at database creation and cannot be changed later.

Tenant‑level : Compatibility is set per tenant and immutable after selection.

Feature‑level : Specific features (e.g., functions, data types) are added to emulate the source database.

3) Compatibility Assessment

Many vendors provide assessment tools or documentation to help users evaluate compatibility, sometimes offering automated analysis and conversion suggestions.

4) Data Migration

Beyond syntax compatibility, the ability to migrate or synchronize data from the source to the target is crucial; the article lists whether each product supplies heterogeneous migration capabilities.

5) Compatibility Items

Protocol : Compatibility with client tools (Navicat, DBeaver, native command‑line clients) without changing connection strings.

Data Types : Impact on data integrity, query efficiency and development effort.

Character Set : Ensuring correct storage and display when moving data between systems.

SQL Syntax : Differences in DDL/DML/DQL extensions that affect migration effort.

Data Objects : Compatibility of tables, indexes, stored procedures, triggers, and their effect on consistency and performance.

Procedural Language : Support for PL/SQL or other procedural extensions.

Built‑in Functions : Availability of equivalent functions for strings, numbers, dates, aggregates, etc.

System Views : Compatibility of virtual tables that simplify administration.

Optimizer Features : Ability to generate efficient execution plans.

Security Features : Support for access control, encryption, auditing, backup, etc.

2. Compatibility Details of Specific Databases

OceanBase

Provides tenant‑level compatibility: a tenant can be created in MySQL‑compatible or Oracle‑compatible mode, which cannot be changed later. Oracle compatibility starts from version V2.x.x, covering most Oracle syntax, PL, security, backup, high‑availability and optimizer features. MySQL compatibility targets MySQL 5.7 (full) and parts of 8.0 (JSON functions). Migration tools include OceanBase Migration Assessment (OMA) for compatibility evaluation and OceanBase Migration Service (OMS) for data transfer and synchronization.

GoldenDB

Supports Oracle and MySQL compatibility. Oracle compatibility follows SQL‑92/99/2003 standards and covers common Oracle syntax. MySQL compatibility is full, adhering to the same SQL standards.

Migration tool: SLOTH, which handles full and incremental data migration between GoldenDB clusters and heterogeneous sources such as Oracle and MySQL.

GaussDB

Offers MultiDB compatibility via the DBCOMPATIBILITY parameter: A (Oracle), B (MySQL), PG (PostgreSQL). Also provides an M‑Compatibility protocol for MySQL connections. Migration and assessment are handled by UGO (Unified Go Online) and DRS (Data Replication Service) for data copy.

TDSQL

Two main variants: TDSQL‑MySQL (highly compatible with MySQL protocol and syntax) and TDSQL‑PostgreSQL (fully compatible with PostgreSQL). An Oracle‑compatible version of TDSQL‑PostgreSQL is also available, supporting Oracle syntax, data types, packages, views, functions, PL/SQL, etc.

PolarDB

PolarDB‑MySQL is 100 % compatible with MySQL 5.6/5.7/8.0. PolarDB‑PG is fully compatible with PostgreSQL 11/14 and highly compatible with Oracle.

Migration ecosystem includes ADAM (Advanced Database & Application Migration) for assessment and DTS (Data Transmission Service) for real‑time data sync.

TiDB

Highly compatible with MySQL protocol and features of MySQL 5.7/8.0. Migration tool: TiDB Data Migration (DM) for full and incremental migration from MySQL/MariaDB.

GreatDB

Fully compatible with MySQL syntax and partially with Oracle. Migration tool: GreatDTS for one‑stop assessment and data migration.

KingBase

Provides extensive Oracle compatibility (syntax, PL/SQL) and MySQL compatibility, allowing near‑zero code changes during migration. Migration tools: KDTS (offline migration) and KFS (synchronization).

DM

Offers a COMPATIBLE_MODE parameter to select compatibility levels (SQL‑92, Oracle, SQL Server, MySQL, etc.). Migration tools include DM DTS for various source‑target combinations and object migration.

GBase

GBase 8s offers broad Oracle compatibility across PL/SQL, packages, functions, DML/DDL, data types, etc. Migration tools are provided by the vendor.

AntDB

Supports SQL 2016, high concurrency and performance, facilitating smooth migration from Oracle. Migration suite: AntDB MTK (Migration ToolKits) for assessment, conversion and data sync across Oracle, MySQL, PostgreSQL and AntDB.

YanshanDB

Compatible with Oracle on syntax, expressions, data types, built‑in functions, system views and PL. Migration platform: YMP (YanshanDB Migration Platform) for assessment, offline migration and data validation.

Klustron

Supports both MySQL and PostgreSQL protocols and SQL syntax, enabling seamless client connections and one‑click data migration using third‑party tools.

HaloDB

Multi‑mode compatibility engine allows switching among PostgreSQL, Oracle, MySQL, Sybase, SQL Server, DB2 via the database_compat_mode parameter; also offers protocol support for MySQL.