diff options
author | unknown <andrey@example.com> | 2006-11-16 14:01:51 +0100 |
---|---|---|
committer | unknown <andrey@example.com> | 2006-11-16 14:01:51 +0100 |
commit | d63fa0a4078985e656e4c057583fc572add8d3a5 (patch) | |
tree | 24e96e21bb2b19afcae7133bcd7191800c783ad8 /myisammrg | |
parent | db42257de8504d78046a6c5227491ce8edaebe29 (diff) | |
download | mariadb-git-d63fa0a4078985e656e4c057583fc572add8d3a5.tar.gz |
Fix for bug#24219 ALTER TABLE ... RENAME TO ... , DISABLE KEYS leads to crash
(this is the 5.0 patch, because 4.1 differs)
There was an improper order of doing chained operations.
To the documentor: ENABLE|DISABLE KEYS combined with RENAME TO, and no other
ALTER TABLE clause, leads to server crash independent of the presence of
indices and data in the table.
mysql-test/r/alter_table.result:
post-merge fix
my locale is utf8, and this breaks non-utf8 stuff when doing manual merge :(
sql/sql_table.cc:
If there is operation on the KEYS, first do it
and then do a rename if there is such. Or, we will crash because
the underlying table has changed.
Diffstat (limited to 'myisammrg')
0 files changed, 0 insertions, 0 deletions