Database abstraction layer: Difference between revisions

Revision as of 13:47, 7 July 2009

Revision as of 23:14, 4 October 2009

Line 1:

{{contextContext|date=October 2009}}{{Unreferenced|date=December 2008}}A '''database abstraction layer''' is an [[application programming interface]] which unifies the communication between a computer application and [[database]]s such as [[MySQL]], [[PostgreSQL]], [[Oracle database|Oracle]] or [[SQLite]]. Traditionally, all database vendors provide their own interface tailored to their products which leaves it to the application programmer to implement code for all database interfaces he would like to support. Database abstraction layers reduce the amount of work by providing a consistent API to the developer and hide the database specifics behind this interface as much as possible. There exist many abstraction layers with different interfaces in numerous programming languages.

== API level abstraction ==

Line 12:

== Arguments for ==

=== Development period ===

Line 26 ⟶ 25:

== Arguments against ==

=== Speed ===

Line 38 ⟶ 36:

Database abstraction layers may limit the number of available database operations to a subset of those supported by the supported database backends. In particular, database abstraction layers may not fully support database backend specific optimization or debugging features.

[[Category:Application programming interfaces]]