References: This issue is a regression of: Bug #26848711.InnoDB: A race condition occurred when acquiring a table lock for a table that was already in memory.The BLOB value was not yet completely inserted. InnoDB: An attempt to read a zero-length BLOB value raised an assertion failure during recovery.References: This issue is a regression of: Bug #23476050.InnoDB: Attempting to acquire an InnoDB ticket while holding a victim transaction lock caused a lock order violation.In the case of a deadlock, the method by which the number of waiting transactions is approximated produced InnoDB: The Variance-Aware Transaction Scheduling algorithm (VATS) tracks the number of transactions waiting for another transaction.A new method of preserving the AUTOINC counter value during a TRUNCATE PARTITION operation was implemented.InnoDB: An in-memory table object for a table being truncated could be opened under improper metadata locking protection.References: This issue is a regression of: Bug #19806106.InnoDB: An invalid assertion was raised when the optimizer chose a prefix index defined on a virtual column.InnoDB: After upgrading to MySQL 8.0.12, table columns including the FTS_DOC_ID column were missing from the INFORMATION_SCHEMA.INNODB_COLUMNS table.InnoDB: In a single thread, two minitransactions latched the first page of a large object value (LOB) while another thread attempted to allocate the page, causing a deadlock.InnoDB: An I/O error returned by an fsync() operation is now treated as a hard error.InnoDB: Checksum mismatches and other issues were caused by concurrent modification of a tablespace header page, and attempting to place a lock on a partially initialized page.Comma and period characters are no longer InnoDB: The ngram full-text search parser permitted comma and period characters to be tokenized as words, which caused an inconsistency between boolean and natural language mode search results.InnoDB: Potential failures related to page allocation for large objects (LOBs) were not sufficiently handled.

The operation now produces an error instead. InnoDB: Attempting to move a table from a discarded file-per-table tablespace to a shared tablespace raised an assertion.InnoDB: An invalid system variable setting raised an assertion.InnoDB: An assertion failure occurred when starting the server with experimental system variables that were unintentionally exposed in normal MySQL builds.InnoDB: An attempt to access freed memory during a checkpoint operation caused the server to exit.InnoDB: Adding a column to a table with a generated column raised an invalid assertion.InnoDB: Large object (LOB) version numbers stored in LOB index entries were left uninitialized at 0 instead of initialized at 1.

InnoDB: New columns added to INFORMATION_SCHEMA.INNODB_TABLES and INFORMATION_SCHEMA.INNODB_COLUMNS tables in 8.0.12 did not appear after upgrading to 8.0.12.

Important Change JSON: The JSON_TABLE() function now automatically decodes base-64 values and prints them using the character set given by the column specification.

How to download sql server on mac free