You are browsing a version that is no longer maintained.
Maintained
5.0 (upcoming) 4.3 (upcoming) 4.2.1 (current) 3.10 (upcoming) 3.9.3
Unmaintained
4.1 4.0 3.8 3.7 3.6 3.5 3.4 3.3 3.2 3.1 3.0

Introduction

The Doctrine database abstraction & access layer (DBAL) offers a lightweight and thin runtime layer around a PDO-like API and a lot of additional, horizontal features like database schema introspection and manipulation through an OO API.

The fact that the Doctrine DBAL abstracts the concrete PDO API away through the use of interfaces that closely resemble the existing PDO API makes it possible to implement custom drivers that may use existing native or self-made APIs. For example, the DBAL ships with a driver for Oracle databases that uses the oci8 extension under the hood.

The following database vendors are currently supported:

  • MySQL
  • Oracle
  • Microsoft SQL Server
  • PostgreSQL
  • SQLite

The Doctrine 2 database layer can be used independently of the object-relational mapper. In order to use the DBAL all you need is the class loader provided by Composer, to be able to autoload the classes:

1<?php

require_once 'vendor/autoload.php';


2


3

Now you are able to load classes that are in the /path/to/doctrine directory like /path/to/doctrine/Doctrine/DBAL/DriverManager.php which we will use later in this documentation to configure our first Doctrine DBAL connection.