Encara no tenim significats per a "myisam".
1You must use identical MyISAM tables to form a single merge table.
2If you're used to casually moving files around with MyISAM, take heed!
3Turns the memory map option on for reading and writing MyISAM tables.
4For example, suppose you're updating a MyISAM table with 100 rows.
5MyISAM caches only the index inside the MySQL process, in the key buffer.
6Thus, InnoDB loads data and creates indexes more slowly than MyISAM.
7Much of the advice in this section assumes you're using only MyISAM tables.
8It can index data stored with InnoDB and other engines, not just MyISAM.
9Let's see how InnoDB and MyISAM lay out the following table:
10Some storage engines, such as MyISAM, cache only the index in MySQL's memory.
11Even though MyISAM has table-level locks, it can append new rows concurrently with reads.
12Oracle provides the InnoDB Hot Backup solution for backing up InnoDB and MyISAM tables.
13Be especially cautious when using string identifiers with MyISAM tables.
14MyISAM uses packed indexes for strings by default, which may make lookups much slower.
15MyISAM requests a 1 KB key block from disk.
16It's practically unusable for MyISAM tables, because they take too long to check and repair.
Myisam a través del temps