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.

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.

collation is utf8mb4_bin. • MySQL 5.7’s default collation is utf8mb4_general_ci. 113 • 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. 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

collation is utf8mb4_bin. • MySQL 5.7’s default collation is utf8mb4_general_ci. 108 • 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. 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

collation is utf8mb4_bin. • MySQL 5.7’s default collation is utf8mb4_general_ci. • MySQL 8.0’s default collation is utf8mb4_0900_ai_ci. • Default SQL mode: • TiDB’s default SQL mode includes these modes: ONLY_FULL_GROUP_BY 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

collation is utf8mb4_bin. • MySQL 5.7’s default collation is utf8mb4_general_ci. • MySQL 8.0’s default collation is utf8mb4_0900_ai_ci. • Default SQL mode: • TiDB’s default SQL mode includes these modes: ONLY_FULL_GROUP_BY 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

collation is utf8mb4_bin. • MySQL 5.7’s default collation is utf8mb4_general_ci. • MySQL 8.0’s default collation is utf8mb4_0900_ai_ci. • Default SQL mode: • TiDB’s default SQL mode includes these modes: ONLY_FULL_GROUP_BY 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

collation is utf8mb4_bin. • MySQL 5.7’s default collation is utf8mb4_general_ci. • MySQL 8.0’s default collation is utf8mb4_0900_ai_ci. • Default SQL mode: • TiDB’s default SQL mode includes these modes: ONLY_FULL_GROUP_BY 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