Databases
From AdminWiki
(Difference between revisions)
m (teh point!) |
m (→MySQL) |
||
| Line 1: | Line 1: | ||
= SQL = | = SQL = | ||
| - | == MySQL == | + | == [MySQL] == |
Database that has a SQL interface. Claims to be ACID<ref name="acid">Atomicity, Consistency, Isolation, Durability. See [http://databases.about.com/od/specificproducts/a/acid.htm The ACID model]</ref>-compliant; tries hard to. Same story as with [[Web Development|PHP]]: Large availability, everybody uses it, hardly the best choice. | Database that has a SQL interface. Claims to be ACID<ref name="acid">Atomicity, Consistency, Isolation, Durability. See [http://databases.about.com/od/specificproducts/a/acid.htm The ACID model]</ref>-compliant; tries hard to. Same story as with [[Web Development|PHP]]: Large availability, everybody uses it, hardly the best choice. | ||
Revision as of 00:43, 25 May 2006
Contents |
SQL
[MySQL]
Database that has a SQL interface. Claims to be ACID[1]-compliant; tries hard to. Same story as with PHP: Large availability, everybody uses it, hardly the best choice.
Food for thought:
PostgresSQL
Full-featured SQL Server. Is ACID[1]-compliant. Needs more maintenance than MySQL.
Food for thought:
Oracle
The commercial behemoth.
LDAP
LDAP systems are like Databases too - often they build on a generic database and provide a more specialised view.
- OpenLDAP/slapd: the open source LDAP daemon
Footnotes
- ↑ 1.1 1.2 Atomicity, Consistency, Isolation, Durability. See The ACID model
