Have any storage engines been removed in MySQL 5.1?
Appendix A. Frequently Asked Questions About MySQL 5.1Yes. MySQL 5.1 no longer supports the BDB storage engine. Any existing BDB tables should be converted to another storage engine before upgrading to MySQL 5.1.
Related QuestionsAre there any new storage engines in MySQL 5.1?
Appendix A. Frequently Asked Questions About MySQL 5.1Falcon support is not available in the standard MySQL 5.1 release. Falcon is available only in a specially forked release of MySQL 5.1. Information is provided here for evaluation purposes only. There have also been significant improvements in existing storage engines, in particular for the NDB storage engine that forms the basis for MySQL Cluster.
Related QuestionsDo the new features in MySQL 5.1 apply to all storage engines?
Appendix A. Frequently Asked Questions About MySQL 5.1See Chapter 14, Storage Engines and Table Types. 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.
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
Appendix? A.? MySQL 5.1 Frequently Asked QuestionsSee Chapter? 14, Storage Engines and Table Types. 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 Network Monitoring and Advisory Service. For more information see http://www.mysql.com/products/enterprise/advisors.html.Related Questions
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 QuestionsWhat MySQL storage engines are supported with DRBD?
Appendix A. MySQL 5.1 Frequently Asked QuestionsAll of the MySQL transactional storage engines are supported by DRBD, including InnoDB and Falcon. For archived or read-only data, MyISAM or Archive can also be used.
Related QuestionsWhere can I obtain complete documentation for MySQL storage engines?
Appendix A. MySQL 5.0 Frequently Asked QuestionsSee Chapter 14, Storage Engines and Table Types. 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.
Related QuestionsDoes MySQL 5.1 have Sequences?
Appendix A. Frequently Asked Questions About MySQL 5.1No. However, MySQL has an AUTO_INCREMENT system, which in MySQL 5.1 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 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 QuestionsHow To See Which Storage Engines Are Supported in Your MySQL Server?
MySQL Tutorials and TipsA collection of 24 FAQs on MySQL transaction management. Clear answers are provided with tutorial exercises on starting and ending transactions; committing and rolling back transactions; transaction isolation levels: read committed and repeatable read; locks and dead locks.
Related QuestionsWhen did MySQL 5.1 become production-ready (GA)?
Appendix A. Frequently Asked Questions About MySQL 5.1MySQL 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.1 have a NOW() function with fractions of seconds?
Appendix A. Frequently Asked Questions About MySQL 5.1No. 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.1 perform ACID transactions?
Appendix A. Frequently Asked Questions About MySQL 5.1Yes. 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 QuestionsDoes MySQL 5.1 have native support for SSL?
Appendix A. Frequently Asked Questions About MySQL 5.1Most 5.1 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.9.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.9.7.5, "Connecting to MySQL Remotely from Windows with SSH".
Related QuestionsCan MySQL 5.1 peform multi-table inserts, updates, and deletes?
Appendix A. Frequently Asked Questions About MySQL 5.1Yes. 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 19.3, "Using Triggers".
Related QuestionsCan MySQL 5.1 stored routines return result sets?
Appendix A. Frequently Asked Questions About MySQL 5.1Stored procedures can, but stored functions cannot. If you perform an ordinary SELECT inside a stored procedure, the result set is returned directly to the client. You need to use the MySQL 4.1 (or above) client-server protocol for this to work. This means that - for instance - in PHP, you need to use the mysqli extension rather than the old mysql extension.
Related QuestionsDoes MySQL 5.1 have statement-level or row-level triggers?
Appendix A. Frequently Asked Questions About MySQL 5.1In MySQL 5.1, all triggers are FOR EACH ROW - that is, the trigger is activated for each row that is inserted, updated, or deleted. MySQL 5.1 does not support triggers using FOR EACH STATEMENT.
Related QuestionsDo MySQL 5.1 stored procedures and functions work with replication?
Appendix A. Frequently Asked Questions About MySQL 5.1Yes, standard actions carried out in stored procedures and functions are replicated from a master MySQL server to a slave server. There are a few limitations that are described in detail in Section 18.4, "Binary Logging of Stored Routines and Triggers".
Related QuestionsDoes MySQL 5.1 have built-in authentication against LDAP directories?
Appendix A. Frequently Asked Questions About MySQL 5.1No. Support for external authentication methods is on the MySQL roadmap as a "rolling feature", which means that we plan to implement it in the future, but we have not yet determined when this will be done. No. Support for roles is on the MySQL roadmap as a "rolling feature", which means that we plan to implement it in the future, but we have not yet determined when this will be done.
Related QuestionsCan MySQL 5.1 peform multiple-table inserts, updates, and deletes?
Appendix A. MySQL 5.1 Frequently Asked QuestionsYes. For the syntax required to perform multiple-table updates, see Section 11.2.10, "UPDATE Syntax"; for that required to perform multiple-table deletes, see Section 11.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 QuestionsWhat storage engines are supported by MySQL Cluster?
MySQL AB :: MySQL 5.1 Reference Manual :: A.10 MySQL 5.1 FAQ...Clustering in MySQL is supported only by the NDB storage engine. That is, in order for a table to be shared between nodes in a cluster, it must be created using ENGINE=NDB (or ENGINE=NDBCLUSTER, which is equivalent). It is possible to create tables using other storage engines (such as MyISAM or InnoDB) on a MySQL server being used for clustering, but these non-NDB tables will not participate in the cluster; they are local to the individual MySQL server instance on which they are created.
Related Questions