SGI Freeware: mysql 4.0.13

mysql-4.0.13: description + notes

MySQL is a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. The MySQL web site has more details. Note that simply installing fw_mysql does not create a mysql user or change ownership of the /var/spool/mysql directory tree.
MySQL version 4.0 has been declared stable, and can now be safely used in production environments. This means that, in the future, only bug fixes will be done for the 4.0 release series, and only critical bug fixes will be done for the older 3.23 series.
This package has been compiled with Berkeley DB and InnoDB transactional tables, and with tcp_wrappers and OpenSSL support.

NOTE: If you are running IRIX 6.5.18, 6.5.19, or 6.5.20 mysqld may experience pthread deadlocks unless you install patch 5119 (f-stream) or 5120 (m-stream).

Upgrading from version 3.23 to 4.0

Once you have installed MySQL 4.0, you can still use your 3.23 tables. During the installation, infact, your databases will not be touched. However, you should take note of the following:

The new security privileges available with MySQL 4.0 can be used only after your databases have been updated to version 4.0.
The ISAM file format still works in MySQL 4.0 but it's deprecated and will be disabled in MySQL 5.0.
If you don't update your databases, you may run into problems when upgrading later to MySQL 4.1 or newer.

To upgrade your tables to version 4.0, you can follow these steps (as a DB administrator):

Run the script /usr/freeware/bin/mysql_fix_privilege_tables to add new privileges and features to the MySQL privilege tables.
Convert your old ISAM files to MyISAM files with the command /usr/freeware/bin/mysql_convert_table_format database_name
This should only be run if all tables in the given database are ISAM or MyISAM tables. If this is not the case you should connect to the MySQL server, select your database, and execute "ALTER TABLE table_name TYPE=MyISAM" on all the ISAM tables.

Once you have upgraded you databases, you can still downgrade to MySQL 3.23.52 or newer if you run into problems with the MySQL 4.0 series. In this case you have to do a mysqldump of any tables using a full-text index and restore these in 3.23 (because 4.0 uses a new format for full-text index).
Client shared libraries compatibility

With MySQL 4.0 the data structures in the client libraries (libmysqlclient.so and its thread safe version, libmysqlclient_r.so) have been changed. If you have any MySQL clients that have been linked against the previous 3.23 shared libraries you must recompile them using the new libraries provided with this package. In order to provide a smooth path to the upgrade, and to support some older SGI freeware packages that still rely on the old client libraries, the 3.23 shared libraries are installed as well as the 4.0 counterparts. Please note that you should not link your applications against the 3.23 shared libraries (and indeed, it's not supported!): they have been retained only for compatibility reasons and will removed once all the SGI freeware packages depending on them will have been updated.
Older clients, especially if linked against the static libraries, should work with MySQL 4.0 server without any problems. Please refer to the installed MySQL documentation for further information.
Special thanks to Andrea Suatoni (a.suatoni@telefonica.net) for helping port this package to IRIX.
To auto-install this package, go back and click on the respective install icon.