that are returned if there is no LIMIT clause LAST_INSERT_ID �→ () Return the value of the AUTOINCREMENT �→ column for the last INSERT ROW_COUNT �→ () The number of rows affected SCHEMA �→ () Synonym arrays were out of bounds when Window Functions are used #12660 – Improve the behavior of the AutoIncrement column when it is implicitly allocated, to keep it consistent with the default mode of MySQL auto-increment auto-increment locking (“consecutive” lock mode): for the implicit allocation of multiple AutoIncrement IDs in a single-line Insert statement, TiDB guarantees the continuity of the al- located values.

that are returned if there is no LIMIT clause LAST_INSERT_ID �→ () Return the value of the AUTOINCREMENT �→ column for the last INSERT ROW_COUNT �→ () The number of rows affected SCHEMA �→ () Synonym arrays were out of bounds when Window Functions are used #12660 – Improve the behavior of the AutoIncrement column when it is implicitly allocated, to keep it consistent with the default mode of MySQL auto-increment auto-increment locking (“consecutive” lock mode): for the implicit allocation of multiple AutoIncrement IDs in a single-line Insert statement, TiDB guarantees the continuity of the al- located values.

that are returned if there is no LIMIT clause LAST_INSERT_ID �→ () Return the value of the AUTOINCREMENT �→ column for the last INSERT ROW_COUNT �→ () The number of rows affected SCHEMA �→ () Synonym arrays were out of bounds when Window Functions are used #12660 – Improve the behavior of the AutoIncrement column when it is implicitly allocated, to keep it consistent with the default mode of MySQL auto-increment auto-increment locking (“consecutive” lock mode): for the implicit allocation of multiple AutoIncrement IDs in a single-line Insert statement, TiDB guarantees the continuity of the al- located values.

4096，减少输出被截断 SQL 的数量，此参数可通过 SQL 动态调整 #12491 • 支持在列属性上添加 AutoRandom 关键字，用于控制系统自动为主键分配随机整数，避免 AutoIncrement 自增主键带来的写入热点问题 #13127 • 支持表级锁 (Table Locks) #11038 • ADMIN SHOW DDL JOBS 支持 LIKE 或 WHERE 语法进行条件过滤 – 修复使用 Window Functions 时发生数组越界的问题 #12660 – 改进 AutoIncrement 列隐式分配时的行为，与 MySQL 自增锁的默认模式 (“consecutive” lock mode) 保 持一致：对于单行 Insert 语句的多个自增 AutoIncrement ID 的隐式分配，TiDB 保证分配值的连续性。 该改进保证 JDBC getGeneratedKeys() 类型数据插入非法年份时，结果为 NULL 而不是 0000 的兼容性问题 #12744 – 改进 AutoIncrement 列隐式分配时的行为，与 MySQL 自增锁的默认模式 (“consecutive” lock mode) 保持 一致：对于单行 Insert 语句的多个自增 AutoIncrement ID 的隐式分配，TiDB 保证分配值的连续性。该 改进保证 JDBC getGeneratedKeys()

4096，减少输出被截断 SQL 的数量，此参数可通过 SQL 动态调整 #12491 • 支持在列属性上添加 AutoRandom 关键字，用于控制系统自动为主键分配随机整数，避免 AutoIncrement 自增主键带来的写入热点问题 #13127 • 支持表级锁 (Table Locks) #11038 • ADMIN SHOW DDL JOBS 支持 LIKE 或 WHERE 语法进行条件过滤 – 修复使用 Window Functions 时发生数组越界的问题 #12660 – 改进 AutoIncrement 列隐式分配时的行为，与 MySQL 自增锁的默认模式 (“consecutive” lock mode) 保 持一致：对于单行 Insert 语句的多个自增 AutoIncrement ID 的隐式分配，TiDB 保证分配值的连续性。 该改进保证 JDBC getGeneratedKeys() 类型数据插入非法年份时，结果为 NULL 而不是 0000 的兼容性问题 #12744 – 改进 AutoIncrement 列隐式分配时的行为，与 MySQL 自增锁的默认模式 (“consecutive” lock mode) 保持 一致：对于单行 Insert 语句的多个自增 AutoIncrement ID 的隐式分配，TiDB 保证分配值的连续性。该 改进保证 JDBC getGeneratedKeys()

that are returned if there is no LIMIT clause LAST_INSERT_ID �→ () Return the value of the AUTOINCREMENT �→ column for the last INSERT ROW_COUNT �→ () The number of rows affected SCHEMA �→ () Synonym arrays were out of bounds when Window Functions are used #12660 – Improve the behavior of the AutoIncrement column when it is implicitly allocated, to keep it consistent with the default mode of MySQL auto-increment auto-increment locking (“consecutive” lock mode): for the implicit allocation of multiple AutoIncrement IDs in a single-line Insert statement, TiDB guarantees the continuity of the al- located values.

4096，减少输出被截断 SQL 的数量，此参数可通过 SQL 动态调整 #12491 • 支持在列属性上添加 AutoRandom 关键字，用于控制系统自动为主键分配随机整数，避免 AutoIncrement 自增主键带来的写入热点问题 #13127 • 支持表级锁 (Table Locks) #11038 • ADMIN SHOW DDL JOBS 支持 LIKE 或 WHERE 语法进行条件过滤 – 修复使用 Window Functions 时发生数组越界的问题 #12660 – 改进 AutoIncrement 列隐式分配时的行为，与 MySQL 自增锁的默认模式 (“consecutive” lock mode) 保 持一致：对于单行 Insert 语句的多个自增 AutoIncrement ID 的隐式分配，TiDB 保证分配值的连续性。 该改进保证 JDBC getGeneratedKeys() 类型数据插入非法年份时，结果为 NULL 而不是 0000 的兼容性问题 #12744 – 改进 AutoIncrement 列隐式分配时的行为，与 MySQL 自增锁的默认模式 (“consecutive” lock mode) 保持 一致：对于单行 Insert 语句的多个自增 AutoIncrement ID 的隐式分配，TiDB 保证分配值的连续性。该 改进保证 JDBC getGeneratedKeys()

that are returned if there is no LIMIT clause LAST_INSERT_ID �→ () Return the value of the AUTOINCREMENT �→ column for the last INSERT ROW_COUNT �→ () The number of rows affected SCHEMA �→ () Synonym arrays were out of bounds when Window Functions are used #12660 • Improve the behavior of the AutoIncrement column when it is implicitly allocated, to keep it consistent with the default mode of MySQL auto-increment auto-increment locking (“consecutive” lock mode): for the implicit allocation of multiple AutoIncrement IDs in a single-line Insert statement, TiDB guarantees the continuity of the al- located values.

4096，减少输出被截断 SQL 的数量，此参数可通过 SQL 动态调整 #12491 • 支持在列属性上添加 AutoRandom 关键字，用于控制系统自动为主键分配随机整数，避免 AutoIncrement 自增主键带来的写入热点问题 #13127 • 支持表级锁 (Table Locks) #11038 • ADMIN SHOW DDL JOBS 支持 LIKE 或 WHERE 语法进行条件过滤 – 修复使用 Window Functions 时发生数组越界的问题 #12660 – 改进 AutoIncrement 列隐式分配时的行为，与 MySQL 自增锁的默认模式 (“consecutive” lock mode) 保 持一致：对于单行 Insert 语句的多个自增 AutoIncrement ID 的隐式分配，TiDB 保证分配值的连续性。 该改进保证 JDBC getGeneratedKeys() 类型数据插入非法年份时，结果为 NULL 而不是 0000 的兼容性问题 #12744 – 改进 AutoIncrement 列隐式分配时的行为，与 MySQL 自增锁的默认模式 (“consecutive” lock mode) 保持 一致：对于单行 Insert 语句的多个自增 AutoIncrement ID 的隐式分配，TiDB 保证分配值的连续性。该 改进保证 JDBC getGeneratedKeys()

Define a Player model, which represents the `players` table. model Player { id Int @id @default(autoincrement()) name String @unique(map: "uk_player_on_name") @db.VarChar(50) coins Decimal @default(0) there is no LIMIT clause 3844 Name Description LAST_INSERT_ID �→ () Return the value of the AUTOINCREMENT �→ column for the last INSERT ROW_COUNT �→ () The number of rows affected SCHEMA �→ () Synonym arrays were out of bounds when Window Functions are used #12660 • Improve the behavior of the AutoIncrement column when it is implicitly allocated, to keep it consistent with the default mode of MySQL auto-increment