<< previous page   --   table of contents   --   next page >>
| | | | | | | |
  • 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
    100 MySQL Technical Reference for Version 4.0.3 It is a good idea to rebuild and reinstall the Msql-Mysql-modules distribution whenever you install a new release of MySQL, particularly if you notice symptoms such as all your DBI scripts dumping core after you upgrade MySQL. 2.5.1  Upgrading From Version 3.23 to Version 4.0 You can use your old data les without any modi cation with Version 4.0.  If you want to move your data from a MySQL 4.0 server to an older server, you have to use mysqldump. Old clients should work with a Version 4.0 server without any problems. The following lists tell what you have to watch out for when upgrading to version 4.0;    MySQL  4.0  has  a  lot  of  new  privileges  in  the  mysql.user  table.   See  Section  4.3.1 [GRANT], page 212. To get these new privileges to work, one must run the mysql_fix_privilege_tables script.  Until this script is run all users have the SHOW DATABASES, CREATE TEMPORARY TABLES,  and  LOCK TABLES  privileges.   SUPER  and  EXECUTE  privileges take their value from PROCESS.  REPLICATION SLAVE and REPLICATION CLIENT take their values from FILE. If you have any scripts that creates new users, you may want to change them to use the new privileges.  If you are not using GRANT commands in the scripts, this is a good time to change your scripts. In version 4.0.2 the option --safe-show-database is deprecated (and no longer does anything).  See Section 4.2.3 [Privileges options], page 195. If you get access denied errors for new users in version 4.0.2, you should check if you need some of the new grants that you didn't need before.  In particular, you will need REPLICATION SLAVE (instead of FILE) for new slaves.    The startup parameters myisam_max_extra_sort_file_size and myisam_max_extra_ sort_file_size are now given in bytes (was megabytes before 4.0.3).  External system locking of MyISAM/ISAM les is now turned of by default.  One can turn this on by doing --external-locking.  (For most users this is never needed).    The following startup variables/options have been renamed: From to. myisam_bulk_insert_tree_size bulk_insert_buffer_size query_cache_startup_type query_cache_type record_buffer read_buffer_size record_rnd_buffer read_rnd_buffer_size sort_buffer sort_buffer_size warnings log-warnings The  startup  options  record_buffer,  sort_buffer  and  warnings  will  still  work  in MySQL 4.0 but are deprecated.    The following SQL variables have changed name. From to. SQL_BIG_TABLES BIG_TABLES SQL_LOW_PRIORITY_UPDATES LOW_PRIORITY_UPDATES
     

    Customer Support CentreMySQL Reference Manual

    Web Hosting Services
    UNIX WEB HOSTING
    MERCHANT ACCOUNTS
    DEDICATED SERVERS
    E-COMMERCE HOSTING
    SUPPORT & FAQ's
    TERMS OF USE
    Domain Services
    DOMAIN
    REGISTRATION
    MANAGE
    YOUR ACCOUNT
    SUPPORT & FAQ's
    TERMS OF USE
    Corporate Info
    ABOUT US
    OUR NETWORK
    CONTACT US
    SITE MAP
    UNIX Web Hosting | Merchant Accounts | Dedicated Hosting | E-Commerce Hosting
    Domain Registration | About Us | Our Network | Contact Us | Site Map
    Our Partners
    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