Home > database >  Where mysql MyISAM and innodb engine in the gap, suitable for use in what scene respectively
Where mysql MyISAM and innodb engine in the gap, suitable for use in what scene respectively

Time:09-26

I know Innodb support level MyISAM full-text search these things their differences, but that in what scenario will use MyISAM engine

CodePudding user response:

Now basically is the innodb unless special requirements

CodePudding user response:

Baidu! Business general use innodb storage, MyISAM this engine you can date partition, used for logging

CodePudding user response:

Does not require the transaction, the pursuit of faster speed,

CodePudding user response:

For example a master-slave library, the main library table can use innodb for efficiency and data security, part from the library table can use MyISAM specially used for report query,

CodePudding user response:

reference
a database can contain different types of tables,

Transaction security table (TST) than the transaction security table (NTST) has several advantages:


Collapse, more secure, even if the MySQL or hardware problems, either automatic recovery, either from the backup and the transaction log restore, you can retrieve the data,

Many statements, you can merge and COMMIT statement at the same time to accept all of them (if the autocommit banned),

You can perform a ROLLBACK to ignore your changes (if the autocommit banned),

All the changes, if the update fails, you back to the original, (with a transaction security table, all changes are permanent),

Transaction security, the storage engine can read those currently used by many update tables provide better deployment,

Although MySQL support several TRANSACTION safety storage engine, to obtain the best results, you should not be mixed in a TRANSACTION that different kinds of table, if you mix sheet type problems occur, for more information, please refer to section 13.4.1, "START the TRANSACTION, the COMMIT and ROLLBACK Syntax",

If you do not specify a configuration value, InnoDB USES the default configuration values, please refer to the section 15.2.3, "InnoDB configuration,"

The transaction security table itself has several advantages, because there is no transaction costs, all advantages can appear:


Faster,

Requires less disk space,

, update needs less memory

You can be in the same statement merger transaction security and the transaction security table to obtain the best
.

CodePudding user response:

MyISAM for transactional consistency requirements is not high, mainly used to perform query operations, such as logging class
  • Related