How has storage engine (table type) support changed in MySQL 5.1 from previous versions?
Appendix A. Frequently Asked Questions About MySQL 5.1Support 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.
Related QuestionsAre there any new storage engines in MySQL 5.0?
Appendix A. MySQL 5.0 Frequently Asked QuestionsYes. The FEDERATED storage engine, new in MySQL 5.0, allows the server to access tables on other (remote) servers. See Section 14.7, "The FEDERATED Storage Engine".
Related QuestionsHave any storage engines been removed in MySQL 5.0?
Appendix A. MySQL 5.0 Frequently Asked QuestionsYes. MySQL 5.0 no longer supports the ISAM storage engine. If you have any existing ISAM tables from previous versions of MySQL, you should convert these to MyISAM before upgrading to MySQL 5.0.
Related QuestionsDoes MySQL 5.0 have native support for SSL?
Appendix A. MySQL 5.0 Frequently Asked QuestionsMost 5.0 binaries have support for SSL connections between the client and server. We can't currently build with the new YaSSL library everywhere, as it's still quite new and does not compile on all platforms yet. See Section 5.8.7, "Using Secure Connections". You can also tunnel a connection via SSH, if (for instance) if the client application doesn't support SSL connections. For an example, see Section 5.8.7.5, "Connecting to MySQL Remotely from Windows with SSH".
Related QuestionsCan MySQL 5.0 peform multi-table inserts, updates, and deletes?
Appendix A. MySQL 5.0 Frequently Asked QuestionsYes. For the syntax required to perform multi-table updates, see Section 13.2.10, "UPDATE Syntax"; for that required to perform multi-table deletes, see Section 13.2.1, "DELETE Syntax". A multi-table insert can be accomplished using a trigger whose FOR EACH ROW clause contains multiple INSERT statements within a BEGIN ... END block. See Section 18.3, "Using Triggers".
Related QuestionsDo the new features in MySQL 5.0 apply to all storage engines?
Appendix A. MySQL 5.0 Frequently Asked QuestionsThe general new features such as views, stored procedures, triggers, INFORMATION_SCHEMA, precision math (DECIMAL column type), and the BIT column type, apply to all storage engines. There are also additions and changes for specific storage engines.
Related QuestionsWhich versions of the MySQL software support Cluster? Do I have to compile from source?
Appendix A. Frequently Asked Questions About MySQL 5.1Cluster is supported in all server binaries in the 5.1 release series for operating systems on which MySQL Cluster is available. See Section 5.2, "mysqld - The MySQL Server". You can determine whether your server has NDB support using either the SHOW VARIABLES LIKE 'have_%' or SHOW ENGINES statement. You can also obtain NDB support by compiling MySQL from source, but it is not necessary to do so simply to use MySQL Cluster.
Related QuestionsWhere can I find information on how to migrate from MySQL 5.0 to MySQL 5.1?
Appendix A. Frequently Asked Questions About MySQL 5.1For detailed upgrade information, see Section 2.11, "Upgrading 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.
Related QuestionsIs PGP for Personal Privacy Version 5.0 compatible with previous versions of PGP?
PGP/Eudora FAQ'sThe full PGP Version 5.0 is fully compatible with previous versions of PGP. The OEM version of PGP that comes with Eudora, supports only DSS/Diffie-Hellman keys. In versions prior to 5.0, PGP used RSA keys exclusively. PGP Version 5.0 introduced DSS/Diffie-Hellman keys. The exclusive use of DSS/Diffie-Hellman keys in the OEM version 5.0 can limit backwards-compatibility. For example, a user of an older version will not be able to verify your signature, nor with they be able to encrypt to you.
Related QuestionsWhich MySQL versions does phpMyAdmin support?
phpMyAdmin 2.5.4 - DocumentationAll MySQL versions from 3.21 till 4.0 are fully supported. Please note that the older your MySQL version is, the more limitations you will have to face. phpMyAdmin provides experimental support for MySQL 4.1. That means that although you can assign character sets to a table or field, phpMyAdmin will not recode the data when inserting or extracting it. Instead, it will still use the character set you specified for the MySQL connection.
Related QuestionsphpMyAdmin 2.8.2.4 - DocumentationAll MySQL versions from 3.23.32 till 5.0 (except for 4.1.0 and 4.1.1) are fully supported. Please note that the older your MySQL version is, the more limitations you will have to face. phpMyAdmin may connect to your MySQL server using php's classic MySQL extension as well as the improved MySQL extension (MySQLi) that is available in php 5.0. Either way, the developers of both extensions recommend to use the classic extension for MySQL 4.0 and below and MySQLi for MySQL 4.1 and newer.Related Questions
Can MySQL 5.0 peform multiple-table inserts, updates, and deletes?
Appendix A. MySQL 5.0 Frequently Asked QuestionsYes. For the syntax required to perform multiple-table updates, see Section 12.2.10, "UPDATE Syntax"; for that required to perform multiple-table deletes, see Section 12.2.1, "DELETE Syntax". A multiple-table insert can be accomplished using a trigger whose FOR EACH ROW clause contains multiple INSERT statements within a BEGIN ... END block. See Section 19.3, "Using Triggers".
Related QuestionsDoes MySQL 5.0 have Sequences?
Appendix A. MySQL 5.0 Frequently Asked QuestionsNo. However, MySQL has an AUTO_INCREMENT system, which in MySQL 5.0 can also handle inserts in a multi-master replication setup. With the --auto-increment-increment and --auto-increment-offset startup options, you can set each server to generate auto-increment values that don't conflict with other servers. The --auto-increment-increment value should be greater than the number of servers, and each server should have a unique offset.
Related QuestionsWhen did MySQL 5.0 become production-ready (GA)?
Appendix A. MySQL 5.0 Frequently Asked QuestionsMySQL 5.0.15 was released for production use on 19 October 2005. We are now working on MySQL 5.1, which is currently in beta.
Related QuestionsDoes MySQL 5.0 have a NOW() function with fractions of seconds?
Appendix A. MySQL 5.0 Frequently Asked QuestionsNo. This is on the MySQL roadmap as a "rolling feature". This means that it is not a flagship feature, but will be implemented, development time permitting. Specific customer demand may change this scheduling. However, MySQL does parse time strings with a fractional component. See Section 11.3.2, "The TIME Type". Yes. MySQL is fully multi-threaded, and will make use of multiple CPUs, provided that the operating system supports them.
Related QuestionsCan MySQL 5.0 perform ACID transactions?
Appendix A. MySQL 5.0 Frequently Asked QuestionsYes. All current MySQL versions support transactions. The InnoDB storage engine offers full ACID transactions with row-level locking, multi-versioning, non-locking repeatable reads, and all four SQL standard isolation levels.
Related QuestionsQ21 : Why am i not seeing all MySQL table types/storage engines ?
Apache2Triad FAQBy default in apache2triad Mysql is configured only with MyISAM table support , so to enable other engines like InnoDB or BerkleyDB see the mysql config file or its CP gui page
Related QuestionsIs MySQL Cluster transaction-safe? What table types does Cluster support?
MySQL AB :: MySQL 5.0 Reference Manual :: 16.10 MySQL Cluste...Yes. MySQL Cluster is enabled for tables created with the NDB storage engine, which supports transactions. NDB is the only MySQL storage engine which supports clustering.
Related QuestionsAppendix A. MySQL 5.1 Frequently Asked QuestionsSee Chapter 12, Storage Engines. That chapter contains information about all MySQL storage engines except for the NDB storage engine used for MySQL Cluster; NDB is covered in Chapter 15, MySQL Cluster. MySQL Enterprise For expert advice about the storage engine(s) most suitable to your circumstances subscribe to the MySQL Enterprise Monitor. For more information see http://www.mysql.com/products/enterprise/advisors.html.Related Questions
