MySQL Bugs: #36104: INFORMATION_SCHEMA.TABLES shows TRANSACTIONAL=1 twice in CREATE

Bug #36104	INFORMATION_SCHEMA.TABLES shows TRANSACTIONAL=1 twice in CREATE_OPTIONS
Submitted:	15 Apr 2008 22:10	Modified:	10 Jun 2008 9:05
Reporter:	Marc Delisle	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Maria storage engine	Severity:	S3 (Non-critical)
Version:	5.1.23a-maria-alpha	OS:	Any
Assigned to:	Guilhem Bichot	CPU Architecture:	Any
Tags:	information_schema, MARIA

Description:
After switching storage type from MARIA to MyISAM, SHOW CREATE TABLE still shows a MARIA table option.

How to repeat:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 597
Server version: 5.1.23a-maria-alpha MySQL Community Server [Maria] (GPL)

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> use test;
Database changed
mysql> create table a(a int) engine=maria transactional=1;
Query OK, 0 rows affected (0.01 sec)

mysql> alter table a engine=myisam;
Query OK, 0 rows affected, 1 warning (0.01 sec)
Records: 0  Duplicates: 0  Warnings: 0

mysql> show create table a;
+-------+----------------------------------------------------------------------------------------------------------------------+
| Table | Create Table                                                                                                         |
+-------+----------------------------------------------------------------------------------------------------------------------+
| a     | CREATE TABLE `a` (
  `a` int(11) DEFAULT NULL
) ENGINE=MyISAM DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1 TRANSACTIONAL=1 |
+-------+----------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

Also, information_schema.TABLES is now reporting this weird information about the same table, in the CREATE_OPTIONS:

page_checksum=1 TRANSACTIONAL=1 transactional=1

Ok, I just read this report:
http://bugs.mysql.com/bug.php?id=34395

so I guess the remaining issue would be the information_schema duplicate option shown.

Thank you for the report.

Closed as duplicate of bug #34395, because last comment.

Should I open a new bug about this aspect of the problem:

"Also, information_schema.TABLES is now reporting this weird information about the same table, in the CREATE_OPTIONS:

page_checksum=1 TRANSACTIONAL=1 transactional=1"

Marc,

thank you for the feedback. I believe this is same problem, so is possible to just stay these 2 bugs linked.

I confirm that in the latest development tree, we get
TRANSACTIONAL=1 transactional=1
in information_schema.TABLES for the Maria table. This duplication is strange.
I changed the bug's title accordingly.

there is duplicate code in sql/sql_show.cc:get_schema_tables_record():

    if (share->transactional != HA_CHOICE_UNDEF)
    {
      ptr= strxmov(ptr, " TRANSACTIONAL=",
                   (share->transactional == HA_CHOICE_YES ? "1" : "0"),
                   NullS);
    }
#ifdef WITH_PARTITION_STORAGE_ENGINE
...
#endif
    if (share->transactional != HA_CHOICE_UNDEF)
      ptr= strxmov(ptr, " transactional=",
                   ha_choice_values[(uint) share->transactional], NullS);
The first block should be removed (the second one is more recent and more consistent with the rest of the function).

Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html

Pushed into 5.1.25-maria-alpha

Pushed into 5.1.25-maria-alpha

Pushed into 5.1.25-maria-alpha