maria-developers team mailing list archive
Mailing list archive
Re: 1cda762: MDEV-6069: Remove old logic for 3.23-to-higher upgrades from upgrade SQL scripts
Are you referring
"When upgrading to MySQL 5.1.18 or later from a previous MySQL version and
scheduled events have been used, the upgrade utilities do not accommodate
changes in event-related system tables. As a workaround, you can dump
events before the upgrade, then restore them from the dump afterward. This
issue was fixed in MySQL 5.1.20." (from
On Thu, Mar 19, 2015 at 1:35 PM, Nirbhay Choubey <nirbhay@xxxxxxxxxxx>
> Hi Serg,
> On Thu, Mar 19, 2015 at 8:02 AM, Sergei Golubchik <serg@xxxxxxxxxxx>
>> Hi, Nirbhay!
>> On Mar 17, Nirbhay Choubey wrote:
>> > revision-id: 1cda762d3f1132e6696e1c451435746db0a1420a
>> > parent(s): b0542b78c866fb32383f759914b10f060d0e14cd
>> > committer: Nirbhay Choubey
>> > branch nick: server
>> > timestamp: 2015-03-17 11:20:49 -0400
>> > message:
>> > MDEV-6069: Remove old logic for 3.23-to-higher upgrades from upgrade
>> SQL scripts
>> > Fix for failing tests.
>> > * Update mysql_system_tables_fix.sql to makeup the differences in system
>> > tables in 5.1.17 (main.system_mysql_db_fix50117)
>> I don't quite understand that.
>> Why these ALTER TABLEs were not needed before?
> The system table structures in 5.1.17 were slightly different from the
> later 5.1 versions.
> While the original/main patch that I prepared was based on a later
> These extra ALTERs would fix the differences.
>> > * Removed system_mysql_db tests for versions 5.0.30 & 4.1.23.
> Mailing list: https://launchpad.net/~maria-developers
> Post to : maria-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~maria-developers
> More help : https://help.launchpad.net/ListHelp