Databases

From AdminWiki

(Difference between revisions)
Jump to: navigation, search
m ([MySQL])
 
(2 intermediate revisions not shown)
Line 13: Line 13:
* [http://habtm.com/articles/2005/05/01/tagging-again-mysql-subselects-suck MySQL subselects suck]
* [http://habtm.com/articles/2005/05/01/tagging-again-mysql-subselects-suck MySQL subselects suck]
-
== [[PostgresSQL]] ==
+
== [[PostgreSQL]] ==
-
Full-featured SQL Server. Is ACID<ref name="acid">a</ref>-compliant. Needs more maintenance than MySQL.
+
Full-featured SQL Server. Is ACID<ref name="acid">a</ref>-compliant. Needs more maintenance than MySQL. Doesn't have native replication support.
Food for thought:
Food for thought:
-
* [http://sql-info.de/postgresql/postgres-gotchas.html PostgresSQL gotchas]
+
* [http://sql-info.de/postgresql/postgres-gotchas.html PostgreSQL gotchas]
== Oracle ==
== Oracle ==
Line 29: Line 29:
* [[OpenLDAP/slapd]]: the open source LDAP daemon
* [[OpenLDAP/slapd]]: the open source LDAP daemon
-
 
+
* [[Novell eDirectory|Novell eDirectory/NLDAP]]: a commercial system
= Footnotes =
= Footnotes =
<references/>
<references/>

Latest revision as of 00:23, 27 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:

PostgreSQL

Full-featured SQL Server. Is ACID[1]-compliant. Needs more maintenance than MySQL. Doesn't have native replication support.

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.

Footnotes

  1. 1.1 1.2 Atomicity, Consistency, Isolation, Durability. See The ACID model
Personal tools