简体   繁体   中英

MyISAM or InnoDB, for safety of data, which should I choose?

MyISAMInnoDB ,为了确保数据安全,我应该选择哪个?

InnoDB is a safer ACID compliant engine with some integrity features that MyISAM lacks. http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html

Clearly, if you are concerned with de safety of your data I would use InnoDB. Would you use an engine that does not support transactions?

MyISAM is used for performance reasons.

InnoDB has better respect of constraints, data integrity and reliability. It supports foreign key constraints and transactions for instance... The documentation compares transaction and nontransation engines .

See, developer and site lard are expecting only safety, but users are expecting fast retrieval.

Only, in InnoDB there is no fulltext support, so we manage in that situtaion.

Is there alternate constraints there, or is there any tips?

Example,

I have postcode file in my table,

I have around 100000 postcodes,

I have autocomplete for postcode, in this situtaion, if I use the MyISAM, I make the filed as fulltext, so my user will not experience a performance issue.

So is there any idea for this creteria?

Basically I am not a database engineer, I am a developer.

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM