H
Hostasaurus@
Guest
RHEL 4.0 may force the issue
With RHEL 4.0 being released two days ago and coming with MySQL 4.1 as the default, guess they're going to have to find out how to make it work. It sounds like not much will actually be needed though according to the release notes:
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/release-notes/es-x86/
which say:
Users should note that there may be compatibility issues when migrating applications or databases from version 3.23.x to 4.1.x of MySQL. A known issue is that the default timestamp format has changed. To address these various issues, the mysqlclient10 package is included to provide the 3.23.x client library (libmysqlclient.so.10) for binary compatibility with applications linked against this legacy library.
Note
While the mysqlclient10 package provides compatibility support with the MySQL 4.1.x server, it does not support the new password encryption method introduced in version 4.1. To enable compatibility with legacy MySQL 3.x-based clients, the old_passwords parameter is enabled by default in the /etc/my.cnf configuration file. If compatibility with old clients is not required, this parameter can be disabled to allow use of the improved password encryption method.
With RHEL 4.0 being released two days ago and coming with MySQL 4.1 as the default, guess they're going to have to find out how to make it work. It sounds like not much will actually be needed though according to the release notes:
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/release-notes/es-x86/
which say:
Users should note that there may be compatibility issues when migrating applications or databases from version 3.23.x to 4.1.x of MySQL. A known issue is that the default timestamp format has changed. To address these various issues, the mysqlclient10 package is included to provide the 3.23.x client library (libmysqlclient.so.10) for binary compatibility with applications linked against this legacy library.
Note
While the mysqlclient10 package provides compatibility support with the MySQL 4.1.x server, it does not support the new password encryption method introduced in version 4.1. To enable compatibility with legacy MySQL 3.x-based clients, the old_passwords parameter is enabled by default in the /etc/my.cnf configuration file. If compatibility with old clients is not required, this parameter can be disabled to allow use of the improved password encryption method.