SpirirHost Support Centre: MySQL Reference Manual p.104

<< previous page -- table of contents -- next page >>

Chapter_1

Chapter_2

Chapter_3

Chapter_4

Chapter_5

Return to Table of Contents

Table of Contents
1. General Information
2. MySQL Installation
3. Tutorial Introduction
4. Database Administration
5. MySQL Optimisation
6. MySQL Language Reference
7. MySQL Table Types
8. MySQL APIs
9. Extending MySQL

104 MySQL Technical Reference for Version 4.0.3 After installing MySQL Version 3.22, you should start the new server and then run the mysql_fix_privilege_tables script. This will add the new privileges that you need to use the GRANT command. If you forget this, you will get Access denied when you try to use ALTER TABLE, CREATE INDEX, or DROP INDEX. If your MySQL root user requires a password, you should give this as an argument to mysql_fix_privilege_tables. The C API interface to mysql_real_connect() has changed. If you have an old client program that calls this function, you must place a 0 for the new db argument (or recode the client to send the db element for faster connections). You must also call mysql_init() before calling mysql_real_connect()! This change was done to allow the new mysql_ options() function to save options in the MYSQL handler structure. The mysqld variable key_buffer has changed names to key_buffer_size, but you can still use the old name in your startup les. 2.5.4 Upgrading from Version 3.20 to Version 3.21 If you are running a version older than Version 3.20.28 and want to switch to Version 3.21, you need to do the following: You can start the mysqld Version 3.21 server with safe_mysqld --old-protocol to use it with clients from a Version 3.20 distribution. In this case, the new client function mysql_ errno() will not return any server error, only CR_UNKNOWN_ERROR (but it works for client errors), and the server uses the old password() checking rather than the new one. If you are not using the --old-protocol option to mysqld, you will need to make the following changes: All client code must be recompiled. If you are using ODBC, you must get the new MyODBC 2.x driver. The script scripts/add_long_password must be run to convert the Password eld in the mysql.user table to CHAR(16). All passwords must be reassigned in the mysql.user table (to get 62-bit rather than 31-bit passwords). The table format hasn't changed, so you don't have to convert any tables. MySQL Version 3.20.28 and above can handle the new user table format without aecting clients. If you have a MySQL version earlier than Version 3.20.28, passwords will no longer work with it if you convert the user table. So to be safe, you should rst upgrade to at least Version 3.20.28 and then upgrade to Version 3.21. The new client code works with a 3.20.x mysqld server, so if you experience problems with 3.21.x, you can use the old 3.20.x server without having to recompile the clients again. If you are not using the --old-protocol option to mysqld, old clients will issue the error message: ERROR: Protocol mismatch. Server Version = 10 Client Version = 9 The new Perl DBI/DBD interface also supports the old mysqlperl interface. The only change you have to make if you use mysqlperl is to change the arguments to the connect() function. The new arguments are: host, database, user, and password (the user and password arguments have changed places). See Section 8.2.2 [Perl DBI Class], page 540.

MySQL Reference Manual

Home
Hosting Plans \| Domain Registration \| About Us \| Contact Us \| Site Map Terms of Use \| Privacy Policy \| Guarantees Merchant Accounts

SpiritHost - web hosting for spiritual and education sites SpiritHit.com - Religious and Spiritual Portal Copyright © 2002 Dyntex Group, Inc. All Rights Reserved

Return to Table of Contents	Back to top

Web Hosting: Manuals & FAQ's

1. Unix-Based Web Hosting
2. Unix Dedicated Servers
3. Windows Dedicated Servers
4. CuteFTP User’s Guide
5. CuteHTML User’s Guide
6. WS_FTP Pro User's Guide
7. Miva Order User's Guide
8. Miva Merchant User's Guide