Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.11.7
-
None
Description
Why a different table_type there ?
MariaDB [pmacontrol]> SHOW FULL TABLES like 'mysql_server'; |
+-------------------------------------+------------+
|
| Tables_in_pmacontrol (mysql_server) | Table_type |
|
+-------------------------------------+------------+
|
| mysql_server | BASE TABLE |
|
+-------------------------------------+------------+
|
1 row in set (0,000 sec) |
|
MariaDB [pmacontrol]> select TABLE_SCHEMA, TABLE_NAME, TABLE_TYPE from information_schema.tables where table_name ='mysql_server'; |
+--------------+--------------+------------------+
|
| TABLE_SCHEMA | TABLE_NAME | TABLE_TYPE |
|
+--------------+--------------+------------------+
|
| pmacontrol | mysql_server | SYSTEM VERSIONED |
|
+--------------+--------------+------------------+
|
1 row in set (0,001 sec) |
|
MariaDB [pmacontrol]> select version();
|
+---------------------------------------------+
|
| version() |
|
+---------------------------------------------+
|
| 10.11.7-MariaDB-1:10.11.7+maria~ubu2204-log | |
+---------------------------------------------+
|
1 row in set (0,000 sec) |
Looks like an omission, indeed. I'd expect values to be the same.
But now, when it was done six years ago in 10.0.1, shall we fix it? Or shall we say "it's a non-standard command, it doesn't have to show standard values, so we keep it the old way for backward compatibility"?
Do you have a preference?