mariadb/mysql-test/r/huge_frm-6224.result

set @save_max_allowed_packet=@@max_allowed_packet;
set global max_allowed_packet=1024*1024*10;
connect con1,localhost,root;
ERROR HY000: The definition for table `t1` is too big
connection default;
disconnect con1;
set global max_allowed_packet=@save_max_allowed_packet;
Updated mtr files to support different compiled in options This allows one to run the test suite even if any of the following options are changed: - character-set-server - collation-server - join-cache-level - log-basename - max-allowed-packet - optimizer-switch - query-cache-size and query-cache-type - skip-name-resolve - table-definition-cache - table-open-cache - Some innodb options etc Changes: - Don't print out the value of system variables as one can't depend on them to being constants. - Don't set global variables to 'default' as the default may not be the same as the test was started with if there was an additional option file. Instead save original value and reset it at end of test. - Test that depends on the latin1 character set should include default_charset.inc or set the character set to latin1 - Test that depends on the original optimizer switch, should include default_optimizer_switch.inc - Test that depends on the value of a specific system variable should set it in the test (like optimizer_use_condition_selectivity) - Split subselect3.test into subselect3.test and subselect3.inc to make it easier to set and reset system variables. - Added .opt files for test that required specfic options that could be changed by external configuration files. - Fixed result files in rockdsb & tokudb that had not been updated for a while. 2019-08-30 15:06:54 +02:00			`set @save_max_allowed_packet=@@max_allowed_packet;`
MDEV-15925 FRM_MAX_SIZE too low for some use cases increase to 1M 2019-01-16 14:46:36 +01:00			`set global max_allowed_packet=1024102410;`
After-merge fix of a result I missed this in commit 9a7281a70396e6bdd2ce10bf328d36909e044ba6 2019-01-23 19:56:52 +01:00			`connect con1,localhost,root;`
MDEV-6224 Incorrect information in file when *.frm is > 256K Reject huge frms at CREATE TABLE, not when it - successfully written - is being opened. Also raise the frm size limit from 256K to 512K 2014-07-08 19:38:26 +02:00			ERROR HY000: The definition for table `t1` is too big
After-merge fix of a result I missed this in commit 9a7281a70396e6bdd2ce10bf328d36909e044ba6 2019-01-23 19:56:52 +01:00			`connection default;`
			`disconnect con1;`
Updated mtr files to support different compiled in options This allows one to run the test suite even if any of the following options are changed: - character-set-server - collation-server - join-cache-level - log-basename - max-allowed-packet - optimizer-switch - query-cache-size and query-cache-type - skip-name-resolve - table-definition-cache - table-open-cache - Some innodb options etc Changes: - Don't print out the value of system variables as one can't depend on them to being constants. - Don't set global variables to 'default' as the default may not be the same as the test was started with if there was an additional option file. Instead save original value and reset it at end of test. - Test that depends on the latin1 character set should include default_charset.inc or set the character set to latin1 - Test that depends on the original optimizer switch, should include default_optimizer_switch.inc - Test that depends on the value of a specific system variable should set it in the test (like optimizer_use_condition_selectivity) - Split subselect3.test into subselect3.test and subselect3.inc to make it easier to set and reset system variables. - Added .opt files for test that required specfic options that could be changed by external configuration files. - Fixed result files in rockdsb & tokudb that had not been updated for a while. 2019-08-30 15:06:54 +02:00			`set global max_allowed_packet=@save_max_allowed_packet;`