Database abstraction layer: Difference between revisions

Revision as of 17:30, 8 June 2019

Revision as of 05:47, 1 October 2019

Line 1:

{{More citations needed|date=September 2014}}

A '''database abstraction layer''' ('''DBAL'''<ref>{{cite book|author1=Tim Ambler|author2=Nicholas Cloud|title=JavaScript Frameworks for Modern Web Dev|url=https://books.google.com/books?id=2IfDCgAAQBAJ&pg=PA346|year=2015|publisher=Apress|isbn=978-1-4842-0662-1|page=346}}</ref> or '''DAL''') is an [[application programming interface]] which unifies the communication between a computer application and [[database]]s such as [[MSSQL|SQL Server]], [[IBM DB2|DB2]], [[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, she, or shethem 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. If an application has such a layer built in, it is called '''database-agnostic'''.<ref>http://searchdatamanagement.techtarget.com/definition/database-agnostic</ref>

== Database levels of abstraction ==