MySQL
From AdminWiki
m (→Database formats) |
m (→Password format) |
||
| Line 15: | Line 15: | ||
== Password format == | == Password format == | ||
| + | |||
| + | If you're using "old" user tables and/or "old" clients to connect to your database make sure to put | ||
| + | |||
| + | old_passwords = 1 | ||
| + | |||
| + | in your my.cnf. | ||
== Auth table changes == | == Auth table changes == | ||
Revision as of 22:34, 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 world ™) have yet to be discovered by us *knocks on wood*.
If you've got any data that is of value to you, you should strongly opt for a transactional database along with an application which utilizes those features.
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.
Password format
If you're using "old" user tables and/or "old" clients to connect to your database make sure to put
old_passwords = 1
in your my.cnf.
