diff options
| author | unknown <davi@mysql.com/endora.local> | 2008-04-04 13:46:05 -0300 |
|---|---|---|
| committer | unknown <davi@mysql.com/endora.local> | 2008-04-04 13:46:05 -0300 |
| commit | ccd31e9dd4ef9ac3266690231626237d13d53e17 (patch) | |
| tree | f806716af343c1097f814df81866976457bc4f56 /mysql-test/t/myisam_use_mmap_basic.test | |
| parent | e12312d82122cdd3743d05a12015385dd79348b6 (diff) | |
| download | mariadb-git-ccd31e9dd4ef9ac3266690231626237d13d53e17.tar.gz | |
Bug#35824: mysql_upgrade does not fix scheduler tables when upgrading from 5.1.23 to 5.1.24
The problem is that when upgrading the event table, the sql_mode
column was always being added instead of being updated to list new
sql_mode values, causing upgrades of the event which already have
a sql_mode column to not be updated to the new sql_mode values.
The solution is to always add first a stub sql_mode column and
subsequently update the column to the new sql_mode values.
scripts/mysql_system_tables_fix.sql:
Always add and update the sql_mode column of the event table.
Diffstat (limited to 'mysql-test/t/myisam_use_mmap_basic.test')
0 files changed, 0 insertions, 0 deletions