Mysql engines

From wikinotes
Revision as of 21:02, 4 September 2022 by Will (talk | contribs) (Created page with "Each table can have it's own engine,<br> performance may suffer if a join is made across two engine types. {| class="wikitable" |- | innodb || write/concurrency optimized (row lock on write) |- | myisam || read optimized (table lock on write) |- | memory || slow, only supports hash indexes, used for temporary tables. |- | federated || defers reads/writes to other databases. slow on joins, aggregates, etc. |- | blackhole || writes not persisted. |- | csv || csvs written...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Each table can have it's own engine,
performance may suffer if a join is made across two engine types.

innodb write/concurrency optimized (row lock on write)
myisam read optimized (table lock on write)
memory slow, only supports hash indexes, used for temporary tables.
federated defers reads/writes to other databases. slow on joins, aggregates, etc.
blackhole writes not persisted.
csv csvs written to a special directory automatically become tables