mariadb/mysql-test/suite/innodb/t/innodb_bug35220.test

--source include/have_innodb.inc
#
# Bug#35220 ALTER TABLE too picky on reserved word "foreign"
# http://bugs.mysql.com/35220
#

SET storage_engine=InnoDB;

# we care only that the following SQL commands do not produce errors
-- disable_query_log
-- disable_result_log

CREATE TABLE bug35220 (foreign_col INT, dummy_cant_delete_all_columns INT);
ALTER TABLE bug35220 DROP foreign_col;
DROP TABLE bug35220;
allow suite.pm to skip combinations that originate from test/include files. storage/innobase/handler/handler0alter.cc: for NEWDATE key_type says unsigned, thus col->prtype says unsigned, but field->flags says signed. Use the same flag for value retrieval that was used for value storage. 2012-02-07 16:22:36 +01:00			`--source include/have_innodb.inc`
Cherry-pick fix for Bug#35220 from innodb-5.0-ss2475 snapshot. Bug#35220: ALTER TABLE too picky on reserved word "foreign" In ALTER TABLE, change the internal parser to search for ``FOREIGN[[:space:]]'' instead of only ``FOREIGN'' when parsing ALTER TABLE ... DROP FOREIGN KEY ...; otherwise it could be mistaken with ALTER TABLE ... DROP foreign_col; (This fix is already present in MySQL 5.1 and higher.) 2008-08-08 02:25:24 +02:00			`#`
			`# Bug#35220 ALTER TABLE too picky on reserved word "foreign"`
			`# http://bugs.mysql.com/35220`
			`#`

			`SET storage_engine=InnoDB;`

			`# we care only that the following SQL commands do not produce errors`
			`-- disable_query_log`
			`-- disable_result_log`

			`CREATE TABLE bug35220 (foreign_col INT, dummy_cant_delete_all_columns INT);`
			`ALTER TABLE bug35220 DROP foreign_col;`
			`DROP TABLE bug35220;`