MySQL 5.1 リファレンスマニュアル :: A Frequently Asked Questions About MySQL 5.1 :: A.9 MySQL 5.1 FAQ — Migration
« A.8 MySQL 5.0 FAQ — INFORMATION_SCHEMA

A.10 MySQL 5.1 FAQ — Security »
Section Navigation      [Toggle]
  • A Frequently Asked Questions About MySQL 5.1
  • A.1 MySQL 5.1 FAQ — General
  • A.2 MySQL 5.1 FAQ — Storage Engines
  • A.3 MySQL 5.1 FAQ — Server SQL Mode
  • A.4 MySQL 5.1 FAQ — Stored Procedures
  • A.5 MySQL 5.1 FAQ — Triggers
  • A.6 MySQL 5.1 FAQ — Stored Routines, Triggers, and Replication
  • A.7 MySQL 5.1 FAQ — Views
  • A.8 MySQL 5.0 FAQ — INFORMATION_SCHEMA
  • A.9 MySQL 5.1 FAQ — Migration
  • A.10 MySQL 5.1 FAQ — Security
  • A.11 MySQL 5.1 FAQ — MySQL Cluster
  • A.12 MySQL 5.1 FAQ — MySQL Chinese, Japanese, and Korean Character Sets
  • A.13 MySQL 5.1 FAQ — Connectors & APIs

A.9. MySQL 5.1 FAQ — Migration

Questions

  • 26.9.1: Where can I find information on how to migrate from MySQL 5.0 to MySQL 5.1?

  • 26.9.2: How has storage engine (table type) support changed in MySQL 5.1 from previous versions?

Questions and Answers

26.9.1: Where can I find information on how to migrate from MySQL 5.0 to MySQL 5.1?

For detailed upgrade information, see 項2.11. 「MySQL のアップグレード」. We recommend that you do not skip a major version when upgrading, but rather complete the process in steps, upgrading from one major version to the next in each step. This may seem more complicated, but it will you save time and trouble — if you encounter problems during the upgrade, their origin will be easier to identify, either by you or — if you have a MySQL Network subscription — by MySQL support.

26.9.2: How has storage engine (table type) support changed in MySQL 5.1 from previous versions?

Storage engine support has changed as follows:

  • Support for ISAM tables was removed in MySQL 5.0 and you should now use the MyISAM storage engine in place of ISAM. To convert a table tblname from ISAM to MyISAM, simply issue a statement such as this one:

    ALTER TABLE tblname ENGINE=MYISAM;
  • Internal RAID for MyISAM tables was also removed in MySQL 5.0. This was formerly used to allow large tables in filesystems that did not support file sizes greater than 2GB. All modern filesystems allow for larger tables; in addition, there are now other solutions such as MERGE tables and views.

  • The VARCHAR column type now retains trailing spaces in all storage engines.

  • MEMORY tables (formerly known as HEAP tables) can also contain VARCHAR columns.

Copyright © 1997, 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices
Top / Previous / Next / Up / Table of Contents
© 2010, Oracle Corporation and/or its affiliates