Upgrading from pre-2.3.0 yields database errors

[tinne]

When upgrading a 2.2.3 to 3.0-rc3 using wp-admin/upgrade.php, three database errors appear signaling that delete_site_transient() misfunctions, as a column value for option_description is not given
(in a way, this is #4921 again).

The upgrade script should either a) give a default value to that column or b) delete it earlier in the upgrade process.

--8<-- (error msgs follow)

WordPress database error: [Field 'option_description' doesn't have a default value]
INSERT INTO options (option_name, option_value, autoload) VALUES ('_transient_doing_cron', '1276472580', 'yes') ON DUPLICATE KEY UPDATE option_name = VALUES(option_name), option_value = VALUES(option_value), autoload = VALUES(autoload)

WordPress database error: [Field 'option_description' doesn't have a default value]
INSERT INTO options (option_name, option_value, autoload) VALUES ('_site_transient_timeout_theme_roots', '1276479782', 'yes') ON DUPLICATE KEY UPDATE option_name = VALUES(option_name), option_value = VALUES(option_value), autoload = VALUES(autoload)

WordPress database error: [Field 'option_description' doesn't have a default value]
INSERT INTO options (option_name, option_value, autoload) VALUES ('_site_transient_theme_roots', 'a:2:{s:15:\"philippus-do-de\";s:7:\"/themes\";s:9:\"twentyten\";s:7:\"/themes\";}', 'yes') ON DUPLICATE KEY UPDATE option_name = VALUES(option_name), option_value = VALUES(option_value), autoload = VALUES(autoload)

[nacin]

I get to update a friend's site from pre 2.3 to 3.0 in the next few weeks. I will watch out for this.

[chriscct7]

Duplicate of #4921.