Bug 146739 - MySQL misses tables after update
Summary: MySQL misses tables after update
Status: VERIFIED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Update Problems (show other bugs)
Version: Beta 2
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Michal Marek
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-30 18:42 UTC by Christian Boltz
Modified: 2006-03-16 14:08 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
rcmysql (7.38 KB, text/plain)
2006-01-31 17:27 UTC, Michal Marek 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Boltz 2006-01-30 18:42:12 UTC 
I installed 10.1 beta2 as update to 10.0 final.

MySQL basically works, but the tables for stored procedures etc. are missing:

mysql> create procedure keep_summary [...]
ERROR 1146 (42S02): Table 'mysql.proc' doesn't exist

I guess this problem does not appear on new installations because MySQL creates fresh tables when database "mysql" does not (yet) exist.

On updates, the "mysql" database already exists, but is incomplete.

-> the required tables for stored procedures, functions, views and triggers
   should be created when updating to MySQL 5.x
Comment 1 Michal Marek 2006-01-31 17:26:09 UTC 
Hi,

thanks for the report. I've modified the rcmysql script to run
mysql_fix_privilege_tables when updating from 4.1 to 5.0. I'll attach the
script so that you can test it. The updated mysql package will appear in
opensuse factory soon.
Comment 2 Michal Marek 2006-01-31 17:27:48 UTC 
Created attachment 65901 [details]
rcmysql

This is the updated init script.
Comment 3 Christian Boltz 2006-02-02 23:30:40 UTC 
Works perfectly - test succeed :-)

Thanks!
Comment 4 Lenz Grimmer 2006-03-16 14:08:21 UTC 
Excellent, thanks a lot for taking care of this! Please note that we have implemented a slightly different solution for this, starting with MySQL 5.0.19 - see http://dev.mysql.com/doc/refman/5.0/en/mysql-upgrade.html for details. It should not be too difficult to support your scheme and making the transition to the new update mechanism we now implemented.