InnoDB: Fixed an issue where the server dropped an internally defined foreign key index when adding a new index and attempted to use a secondary index defined on a This resulted in an error on restart indicating that it could not locate the tablespace data file. InnoDB failed to update INNODB_SYS_DATAFILES data dictionary table. Fixed an issue where after a RENAME TABLE operation that moved a table to a different schema, InnoDB: Backport of fix for Community Bug #25189192, Bug #84038. With this fix, an invalid character set causes SQL_TEXT column truncation and prevents server exits. As a result, the SQL query text character set could be invalid, which could result in a Table identifies additional MySQL bugs that have been fixed by Aurora MySQL database engine updates, andįixed an issue where the code for reading character set information from Performance Schema statement events tables (for example, events_statements_current)ĭid not prevent simultaneous writing to that character set information. MySQL 5.7-compatible version Aurora contains all MySQL bug fixes through MySQL 5.7.40. MySQL bugs fixed by Aurora MySQL 2.x database That could result in unexpected server behavior. Upgrades to this version aren't supported. (Bug #32416811)Īurora MySQL database engine updates (version 3.01.1, compatible with MySQL 8.0.23) The end of standard support is January 15, 2024. Upgrades to this version aren't supported.įixed the improper handling of temporary tables used for cursors within stored procedures (Compatible with MySQL 5.7) to Aurora MySQL version 3 (Compatible with MySQL 8.0) (Bug #33919635)Īurora MySQL database engine updates (version 3.02.0, compatible with MySQL 8.0.23) The end of standard support is January 15, 2024. Assignment of these table IDs may result in conflicting data dictionary table IDs while upgrading from Aurora MySQL version 2 (Bug #87926, Bug #26906787)įixed an issue which can lead to a failure while upgrading an Aurora MySQL version 1 (Compatible with MySQL 5.6) database cluster containing user-created The previous valid AUTO_INCREMENT value should have been returned in this case, causing a duplicate key error. The error was due to the maximum column value not being considered. Incorrect AUTO_INCREMENT values were generated when the maximum integer column value was exceeded. That were deleted and recreated between executions, did not execute correctly for subsequent invocations following the first one. (Bug #33578113)įixed an issue where a stored procedure containing an IF statement using EXISTS, which acted on one or more tables (Bug #34060289)įixed an issue where it wasn't possible to revoke the DROP privilege on the Performance Schema. The query includes a left join and an IN subquery. (Bug #32855634).įixed an issue where a query that references a view in a subquery and an outer query block can cause an unexpected restart (Bug#32324234)Īurora MySQL database engine updates (version 3.02.2, compatible with MySQL 8.0.23) The end of standard support is January 15, 2024.Ī derived table is merged into the outer query block. (Bug #33578113)įixed an issue where a stored procedure containing an IF statement using EXISTS, which acted on one or more tables that were deleted and recreated between executions, did not execute correctly for subsequent invocations following the first one. (Bug #87926, Bug #26906787)įixed an issue where it was not possible to revoke the DROP privilege on the Performance Schema. The query includes a left join and an IN subqueryįixed an issue where incorrect AUTO_INCREMENT values were generated when the maximum integer column value was exceeded. A derived table is merged into the outer query block
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |