diff options
author | unknown <kaa@mbp.local> | 2008-02-01 13:00:40 +0500 |
---|---|---|
committer | unknown <kaa@mbp.local> | 2008-02-01 13:00:40 +0500 |
commit | 653ab4eeaab60e7eb239c53ec8125683ba1ed697 (patch) | |
tree | db2f46689e159d75cd24ebf189781616442b2aae /sql-common | |
parent | f6bbfa4a75731a5abfcf52696d09ca730a65c566 (diff) | |
download | mariadb-git-653ab4eeaab60e7eb239c53ec8125683ba1ed697.tar.gz |
Fix for bug #25162: Backing up DB from 5.1 adds 'USING BTREE' to KEYs
on table creates
The problem was in incompatible syntax for key definition in CREATE
TABLE.
5.0 supports only the following syntax for key definition (see "CREATE
TABLE syntax" in the manual):
{INDEX|KEY} [index_name] [index_type] (index_col_name,...)
While 5.1 parser supports the above syntax, the "preferred" syntax was
changed to:
{INDEX|KEY} [index_name] (index_col_name,...) [index_type]
The above syntax is used in 5.1 for the SHOW CREATE TABLE output, which
led to dumps generated by 5.1 being incompatible with 5.0.
Fixed by changing the parser in 5.0 to support both 5.0 and 5.1 syntax
for key definition.
mysql-test/r/create.result:
Added a test case for bug #25162.
mysql-test/t/create.test:
Added a test case for bug #25162.
sql/sql_yacc.yy:
Changed the parser to support both 5.0 and 5.1 syntax for index type
specification in CREATE TABLE.
Diffstat (limited to 'sql-common')
0 files changed, 0 insertions, 0 deletions