MySQL
From AdminWiki
(Difference between revisions)
(initial commit) |
m (→Database formats) |
||
| Line 6: | Line 6: | ||
== Database formats == | == Database formats == | ||
| - | MySQL currently offers two database formats. MyISAM is the non-transactional in-place updating table. Think of it more like a relational textfile than a real database. InnoDB is the relational table-format, which MySQL promotes as being ACID-conform. It's less mature than MyISAM and it's behaviour with semi-corrupted tables (these things | + | MySQL currently offers two database formats. MyISAM is the non-transactional in-place updating table. Think of it more like a relational textfile than a real database. InnoDB is the relational table-format, which MySQL promotes as being ACID-conform. It's less mature than MyISAM and it's behaviour with semi-corrupted tables (these things happen in the real word (tm)) have yet to be discovered by us *knocks on wood*. |
| - | + | ||
= Migration woes = | = Migration woes = | ||
Revision as of 21:24, 26 May 2006
Contents |
Introduction
MySQL is the defacto standard database in the opensource world, but it's reign isn't undisputed. See the link list on the Databases page.
Database formats
MySQL currently offers two database formats. MyISAM is the non-transactional in-place updating table. Think of it more like a relational textfile than a real database. InnoDB is the relational table-format, which MySQL promotes as being ACID-conform. It's less mature than MyISAM and it's behaviour with semi-corrupted tables (these things happen in the real word (tm)) have yet to be discovered by us *knocks on wood*.
Migration woes
Since 3.23 a few things have changed. Depending on the version jump one or more of those points may apply to you.
