[MDEV-21537] InnoDB INFORMATION_SCHEMA tables fail to define DEFAULT for ENUM NOT NULL Created: 2020-01-20  Updated: 2021-12-28  Resolved: 2020-01-22

Status: Closed
Project: MariaDB Server
Component/s: Information Schema, Storage Engine - InnoDB
Affects Version/s: 10.5.0
Fix Version/s: 10.5.1

Type: Bug Priority: Major
Reporter: Marko Mäkelä Assignee: Alexander Barkov
Resolution: Fixed Votes: 0
Labels: regression

Issue Links:
Problem/Incident
is caused by MDEV-19940 Clean up INFORMATION_SCHEMA.INNODB_ t... Closed
Relates
relates to MDEV-20254 Problems with EMPTY_STRING_IS_NULL an... Closed

 Description   

The recently added test innodb.innodb_wl6326_big fails because of a change that was introduced in MDEV-19940:

CURRENT_TEST: innodb.innodb_wl6326_big
 
mysqltest: At line 157: query 'CREATE TABLE my_metrics LIKE information_schema.innodb_metrics' failed: 1067: Invalid default value for 'TYPE'

The column information_schema.innodb_metrics.type used to be declared VARCHAR…NOT NULL DEFAULT '', but now it is ENUM…NOT NULL DEFAULT ''. A proper default value should be declared.

 Comments   
Comment by Marko Mäkelä [ 2020-01-22 ]

After the fix, the ENUM…NOT NULL columns in INFORMATION_SCHEMA.INNODB_% tables will not report any DEFAULT value at all. Default values do not make sense for read-only tables.

Generated at Thu Feb 08 09:07:53 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.