Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.0.14
-
None
Description
If you create a view with ALGORITHM=MERGE or ALGORITHM=TEMPTABLE in MySQL 5.1 (or actually I believe in any version of MySQL) and then start MariaDB on the same data the algorithm in the view definition gets changed to the opposite one (MERGE -> TEMPTABLE and TEMPTABLE -> MERGE).
The problem is in this commit: http://bazaar.launchpad.net/~maria-captains/maria/10.0/revision/2502.557.1 which was made in response to this bug https://bugs.launchpad.net/maria/+bug/983285.
If you look closely comment #2 on the bug says: "In 5.2 numeric algorithm values are: undefined=0, temptable=1, merge=2." If you look at sql/table.h in the commit you'll see:
#define VIEW_ALGORITHM_MERGE_FRM 1
|
#define VIEW_ALGORITHM_TMPTABLE_FRM 2
|
So the numeric values stored in the frm file (and thus interpretation of the values written in the frm file) got reversed and sadly nobody noticed that. Now it will break any upgrade from MySQL to MariaDB.
revno: 4407
revision-id: sanja@askmonty.org-20150209014828-kx3cr36hgrvjhtrg
parent: svoj@mariadb.org-20150114135038-v50g2cul4vce63h8
committer: sanja@askmonty.org
branch nick: work-maria-5.5-
MDEV-6916-check_viewtimestamp: Mon 2015-02-09 02:48:28 +0100
message:
MDEV-6916: Upgrade from MySQL to MariaDB breaks already created viewsCHECK/REPAIR commands and mysql_upgradesupport for upgrade from MySQL server support.