manuel Using Firebird, distribué sur le CD-ROM de IBPhoenix. Le Guide de démarrage de Firebird était à l'origine le Chapitre 1 du manuel Using Firebird, vendu sur CD par IBPhoenix. Plus tard, il a été publié cela dépend de votre configuration. Un rapide aperçu des différences les plus importantes sont listées ci après. Firebird 1.5 Guide de démarrage 4 Tableau 1. Firebird 1.5 Classic Server vs. Superserver Note Une base de données en lecture seule peut résider sur un CD-ROM mais vous ne pouvez pas exécuter le serveur Firebird à partir de celui-ci. Script d'installation ou programme Bien qu’ il soit possible

trans formation None None Relevant interface Co nsistency Not support Support Eventual consistency Isolation Not support Support Business‐side guarantee Co ncurrency pe rformance No influence Serious ShardingSphere from GitHub,Then compile. git clone --depth 1 https://github.com/apache/shardingsphere.git cd shardingsphere mvn clean install -Dmaven.javadoc.skip=true -Dcheckstyle.skip=true -Drat.skip=true ShardingSphere document, v5.1.1 Name Descrip- tion Value range Default value JVM _IN‐ FORMA‐ TION_CO LLEC‐ TOR_ENABLED Start JVM collector true、false true SER‐ VICE_NAME Tracking service name

trans formation None None Relevant interface Co nsistency Not support Support Eventual consistency Isolation Not support Support Business‐side guarantee Co ncurrency pe rformance No influence Serious ShardingSphere from GitHub,Then compile. git clone --depth 1 https://github.com/apache/shardingsphere.git cd shardingsphere mvn clean install -Dmaven.javadoc.skip=true -Dcheckstyle.skip=true -Drat.skip=true ShardingSphere document, v5.1.2 Name Descrip- tion Value range Default value JVM _IN‐ FORMA‐ TION_CO LLEC‐ TOR_ENABLED Start JVM collector true, false true SER‐ VICE_NAME Tracking service name

Firebird 2.1: • Тип данных SQL_NULL • Набор символов GB18030, алиас для WIN_1258 • Сортировка UNICODE_CI_AI для UTF8, сортировка GB18030 для GB18030 Язык определения данных (DDL) Изменения начиная с Firebird неполная; сортировки в пустых полях этой колонки могут быть регистрочувствительными (case insensitive — ci), акцентно нечувствительными / диакритически чувствительными (accent insensitive — ai) или словарно Chinese 2.5 GBK GBK_UNICODE Chinese 2.1 ISO8859_1 ES_ES_CI_AI Spanish ci, ai 2.0 FR_FR_CI_AI French ci, ai 2.1 PT_BR Brazilian Portuguese ci, ai 2.0 ISO8859_2 CS_CZ Czech 1.0 ISO_HUN Hungarian 1

supported Not supported Final consistency I solation Not supported Supported Business side guaran‐ teed Co ncurrent per formance no loss severe loss slight loss Applied s cenar‐ ios Inconsistent processing default AuditStrategy (?) ShardingAuditSt rate‐ gyConfiguration Default key auditor DML_SHA RDING_CO NDITIONS defaultS hardingCol‐ umn (?) String Default sharding col‐ umn name None shard ingAlgorithms EncryptTableRuleConfiguration Attributes: Name DataType Description name String Table name columns (+) Co llection Encrypt column rule configura‐ tions Encrypt Column

Capture and incremental backup and restore. • Data is scoped according to different usage and supports co-existence of a single TiDB cluster, Transactional KV, RawKV applications. Due to significant changes The default collation of utf8mb4 in MySQL 5.7 is utf8mb4_general_ci. • The default collation of utf8mb4 in MySQL 8.0 is utf8mb4_0900_ai_ci. • Default value of foreign_key_checks: • The default value in Processing (OLAP). • Storage engines of HTAP: The row-based storage engine and the columnar storage engine co-exist for HTAP. Both storage engines can replicate data automatically and keep strong consistency.

@lcwangchao • Fix the issue that query results are incorrect due to STREAM_AGG() incorrectly handling CI #49902 @wshwsh12 • Fix the issue that encoding fails when converting bytes to TIME #47346 @wshwsh12 collation is utf8mb4_bin. • MySQL 5.7’s default collation is utf8mb4_general_ci. 93 • MySQL 8.0’s default collation is utf8mb4_0900_ai_ci. • Default SQL mode: • TiDB’s default SQL mode includes these modes: Processing (OLAP). • Storage engines of HTAP: The row-based storage engine and the columnar storage engine co-exist for HTAP. Both storage engines can replicate data automatically and keep strong consistency.

supported Supported Final consistency I solation Not supported Supported Business side guaran‐ teed Co ncurrent per formance no loss severe loss slight loss Applied s cenar‐ ios Inconsistent processing default AuditStrategy (?) ShardingAuditSt rate‐ gyConfiguration Default key auditor DML_SHA RDING_CO NDITIONS defaultS hardingCol‐ umn (?) String Default sharding col‐ umn name None shard ingAlgorithms EncryptTableRuleConfiguration Attributes: Name DataType Description name String Table name columns (+) Co llection Encrypt column rule configura‐ tions Encrypt Column

The default collation of utf8mb4 in MySQL 5.7 is utf8mb4_general_ci. • The default collation of utf8mb4 in MySQL 8.0 is utf8mb4_0900_ai_ci. • Default value of foreign_key_checks: • The default value in Processing (OLAP). • Storage engines of HTAP: The row-based storage engine and the columnar storage engine co-exist for HTAP. Both storage engines can replicate data automatically and keep strong consistency. Transactional Processing (OLTP) and a columnar storage engine TiFlash for Online Analytical Processing (OLAP) co-exist, replicate data automatically, and keep strong consistency. For more information about the architecture

default character set is utf8mb4, and the default �→ collation of utf8mb4 is utf8mb4_0900_ai_ci. TiDB v7.4.0 �→ adding support for this enhances compatibility with MySQL 8.0 so that �→ migrations collation is utf8mb4_bin. • MySQL 5.7’s default collation is utf8mb4_general_ci. 80 • MySQL 8.0’s default collation is utf8mb4_0900_ai_ci. • Default SQL mode: • TiDB’s default SQL mode includes these modes: Processing (OLAP). • Storage engines of HTAP: The row-based storage engine and the columnar storage engine co-exist for HTAP. Both storage engines can replicate data automatically and keep strong consistency.