« Changelog History


tidb v3.0.11 Release Notes

Release Date: 2020-03-04 // about 4 years ago

  • Compatibility Changes

    • ➕ Add the max-index-length configuration item to control the maximum index length, which is compatible with the behavior of TiDB versions before 3.0.7 or of MySQL #15057

    🆕 New Features

    • 👌 Support showing the meta information of partitioned tables in the information_schema.PARTITIONS table #14849

    🛠 Bugfixes

    • 🛠 Fix the issue of Goroutine leaks when retrying an optimistic transaction because queries using Union are not marked read-only #15076
    • Fix the issue that SHOW TABLE STATUS fails to correctly output the table status at the snapshot time because the value of the tidb_snapshot parameter is not correctly used when executing the SET SESSION tidb_snapshot = 'xxx'; statement #14391
    • 🛠 Fix the incorrect result caused by a SQL statement that contains Sort Merge Join and ORDER BY DESC at the same time #14664
    • 🛠 Fix the panic of TiDB server when creating partition tables using the unsupported expression. The error information This partition function is not allowed is returned after fixing this panic. #14769
    • 🛠 Fix the incorrect result occurred when executing the select max() from subquery statement with the subquery containing Union #14944
    • 🛠 Fix the issue that an error message is returned when executing the SHOW BINDINGS statement after executing DROP BINDING that drops the execution binding #14865
    • 🛠 Fix the issue that the connection is broken because the maximum length of an alias in a query is 256 characters in the MySQL protocol, but TiDB does not [cut the alias] (https://dev.mysql.com/doc/refman/8.0/en/identifier-length.html) in the query results according to this protocol #14940
    • 🛠 Fix the incorrect query result that might occur when using the string type in DIV. For instance, now you can correctly execute the select 1 / '2007' div 1 statement 14098