diff options
author | Ramil Kalimullin <ramil@mysql.com> | 2008-08-26 18:48:50 +0500 |
---|---|---|
committer | Ramil Kalimullin <ramil@mysql.com> | 2008-08-26 18:48:50 +0500 |
commit | 4d5670ebf9ce20823983d3c972597020c6acb36b (patch) | |
tree | 394f2027a5da1365dc8bcf00213ccf58b8d61289 /myisam | |
parent | d7445d0493a6845f2428303776f9e18b500f2e5b (diff) | |
download | mariadb-git-4d5670ebf9ce20823983d3c972597020c6acb36b.tar.gz |
Fix for bug #37310: 'on update CURRENT_TIMESTAMP' option crashes the table
Problem: data consistency check (maximum record length) for a correct
MyISAM table with CHECKSUM=1 and ROW_FORMAT=DYNAMIC option
may fail due to wrong inner MyISAM parameter. In result we may
have the table marked as 'corrupted'.
Fix: properly set MyISAM maximum record length parameter.
Diffstat (limited to 'myisam')
-rw-r--r-- | myisam/mi_create.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/myisam/mi_create.c b/myisam/mi_create.c index 75863ed976f..bb53393c345 100644 --- a/myisam/mi_create.c +++ b/myisam/mi_create.c @@ -192,7 +192,7 @@ int mi_create(const char *name,uint keys,MI_KEYDEF *keydefs, packed=(packed+7)/8; if (pack_reclength != INT_MAX32) pack_reclength+= reclength+packed + - test(test_all_bits(options, HA_OPTION_CHECKSUM | HA_PACK_RECORD)); + test(test_all_bits(options, HA_OPTION_CHECKSUM | HA_OPTION_PACK_RECORD)); min_pack_length+=packed; if (!ci->data_file_length && ci->max_rows) |