This guide covers getting started with the Doctrine ORM. After working through the guide you should know:
- How to install and configure Doctrine by connecting it to a database
- Mapping PHP objects to database tables
- Generating a database schema from PHP objects
- Using the
EntityManagerto insert, update, delete and find objects in the database.
This guide is designed for beginners that haven’t worked with Doctrine ORM before. There are some prerequesites for the tutorial that have to be installed:
- PHP (latest stable version)
- Composer Package Manager(Install Composer)
The code of this tutorial is available on Github.
Doctrine 2 is an object-relational mapper (ORM) for PHP 5.4+ that provides transparent persistence for PHP objects. It uses the Data Mapper pattern at the heart, aiming for a complete separation of your domain/business logic from the persistence in a relational database management system.
The benefit of Doctrine for the programmer is the ability to focus on the object-oriented business logic and worry about persistence only as a secondary problem. This doesn’t mean persistence is downplayed by Doctrine 2, however it is our belief that there are considerable benefits for object-oriented programming if persistence and entities are kept separated.
Entities are PHP Objects that can be identified over many requests by a unique identifier or primary key. These classes don’t need to extend any abstract base class or interface. An entity class must not be final or contain final methods. Additionally it must not implement clone nor wakeup, unless it does so safely.
An entity contains persistable properties. A persistable property is an instance variable of the entity that is saved into and retrieved from the database by Doctrine’s data mapping capabilities.
For this Getting Started Guide for Doctrine we will implement the Bug Tracker domain model from the Zend_Db_Table documentation. Reading their documentation we can extract the requirements:
- A Bug has a description, creation date, status, reporter and engineer
- A Bug can occur on different Products (platforms)
- A Product has a name.
- Bug reporters and engineers are both Users of the system.
- A User can create new Bugs.
- The assigned engineer can close a Bug.
- A User can see all his reported or assigned Bugs.
- Bugs can be paginated through a list-view.
Create a new empty folder for this tutorial project, for example doctrine2-tutorial and create a new file
composer.json with the following contents:
Install Doctrine using the Composer Dependency Management tool, by calling:
This will install the packages Doctrine Common, Doctrine DBAL, Doctrine ORM, Symfony YAML and Symfony Console into the vendor directory. The Symfony dependencies are not required by Doctrine but will be used in this tutorial.
Add the following directories:
Doctrine’s public interface is the EntityManager, it provides the access point to the complete lifecycle management of your entities and transforms entities from and back to persistence. You have to configure and create it to use your entities with Doctrine 2. I will show the configuration steps and then discuss them step by step:
The first require statement sets up the autoloading capabilities of Doctrine using the Composer autoload.
The second block consists of the instantiation of the ORM Configuration object using the Setup helper. It assumes a bunch of defaults that you don’t have to bother about for now. You can read up on the configuration details in the reference chapter on configuration.
The third block shows the configuration options required to connect to a database, in my case a file-based sqlite database. All the configuration options for all the shipped drivers are given in the DBAL Configuration section of the manual.
The last block shows how the EntityManager is obtained from a factory method.
Now that we have defined the Metadata mappings and bootstrapped the EntityManager we want to generate the relational database schema from it. Doctrine has a Command-Line Interface that allows you to access the SchemaTool, a component that generates the required tables to work with the metadata.
For the command-line tool to work a
cli-config.php file has to be present in the project root directory, where you will execute the doctrine command. Its a fairly simple file:
You can then change into your project directory and call the Doctrine command-line tool:
At this point no entity metadata exists in src so you will see a message like “No Metadata Classes to process”. Don’t worry, we’ll create a Product entity and corresponding metadata in the next section.
You should be aware that during the development process you’ll periodically need to update your database schema to be in sync with your Entities metadata.
You can easily recreate the database:
vendor/bin/doctrine orm:schema-tool:drop --force
Or use the update functionality:
vendor/bin/doctrine orm:schema-tool:update --force
The updating of databases uses a Diff Algorithm for a given Database Schema, a cornerstone of the Doctrine\DBAL package, which can even be used without the Doctrine ORM package.
We start with the simplest entity, the Product. Create a
src/Product.php file to contain the Product entity definition:
Note that all fields are set to protected (not public) with a mutator (getter and setter) defined for every field except $id. The use of mutators allows Doctrine to hook into calls which manipulate the entities in ways that it could not if you just directly set the values with
entity#field = foo;
The id field has no setter since, generally speaking, your code should not set this value since it represents a database id value. (Note that Doctrine itself can still set the value using the Reflection API instead of a defined setter function)
The next step for persistence with Doctrine is to describe the structure of the Product entity to Doctrine using a metadata language. The metadata language describes how entities, their properties and references should be persisted and what constraints should be applied to them.
Metadata for entities are configured using a XML, YAML or Docblock Annotations. This Getting Started Guide will show the mappings for all Mapping Drivers. References in the text will be made to the XML mapping.
<!-- config/xml/Product.dcm.xml -->
The top-level entity definition tag specifies information about the class and table-name. The primitive type Product#name is defined as a field attribute. The id property is defined with the id tag, this has a generator tag nested inside which defines that the primary key generation mechanism automatically uses the database platforms native id generation strategy (for example AUTO INCREMENT in the case of MySql or Sequences in the case of PostgreSql and Oracle).
Now that we have defined our first entity, let’s update the database:
$ vendor/bin/doctrine orm:schema-tool:update --force --dump-sql
Specifying both flags
--dump-sql prints and executes the DDL statements.
Now create a new script that will insert products into the database:
Call this script from the command-line to see how new products are created:
php create_product.php ORM php create_product.php DBAL
Here I got some errors:
$ php create_product.php ORM
Thanks for the PhpStrom “PHP Annotations” plugin!!! It generated codes like this:
use Doctrine\ORM\Mapping as ORM;
* Created by PhpStorm.
* User: xiyusullos
* Date: 2017/3/9
* Time: 15:29
* @ORM\Entity() @ORM\Table(name="products")
* @var int
* @ORM\Id() @ORM\Column(type="integer") @ORM\GeneratedValue()
* @var string
One more important is that only double quote works. This
@Table(name='products')doesn’t work. Make sure change the ’ to " like
What is happening here? Using the Product is pretty standard OOP. The interesting bits are the use of the EntityManager service. To notify the EntityManager that a new entity should be inserted into the database you have to call persist(). To initiate a transaction to actually perform the insertion, You have to explicitly call flush() on the EntityManager.
This distinction between persist and flush is allows to aggregate all writes (INSERT, UPDATE, DELETE) into one single transaction, which is executed when flush is called. Using this approach the write-performance is significantly better than in a scenario where updates are done for each entity in isolation.
Doctrine follows the UnitOfWork pattern(Intent: Maintains a list of objects that are affected by a business transaction and coordinates the writing out of changes and resolution of concurrency problems.) which additionally detects all entities that were fetched and have changed during the request. You don’t have to keep track of entities yourself, when Doctrine already knows about them.
As a next step we want to fetch a list of all the Products. Let’s create a new script for this:
EntityManager#getRepository() method can create a finder object (called a repository) for every entity. It is provided by Doctrine and contains some finder methods such as
Let’s continue with displaying the name of a product based on its ID:
Updating a product name demonstrates the functionality UnitOfWork of pattern discussed before. We only need to find a product entity and all changes to its properties are written to the database:
After calling this script on one of the existing products, you can verify the product name changed by calling the
We continue with the bug tracker domain, by creating the missing classes Bug and User and putting them into src/Bug.php and src/User.php respectively.
All of the properties discussed so far are simple string and integer values, for example the id fields of the entities, their names, description, status and change dates. Next we will model the dynamic relationships between the entities by defining the references between entities.
References between objects are foreign keys in the database. You never have to (and never should) work with the foreign keys directly, only with the objects that represent the foreign key through their own identity.
For every foreign key you either have a Doctrine ManyToOne or OneToOne association. On the inverse sides of these foreign keys you can have OneToMany associations. Obviously you can have ManyToMany associations that connect two tables with each other through a join table with two foreign keys.
Now that you know the basics about references in Doctrine, we can extend the domain model to match the requirements:
You use Doctrine’s ArrayCollections in your Doctrine models, rather than plain PHP arrays, so that Doctrine can watch what happens with them and act appropriately. Note that if you dump your entities, you’ll see a “PersistentCollection” in place of your ArrayCollection, which is just an internal Doctrine class with the same interface.
Lazy load proxies always contain an instance of Doctrine’s EntityManager and all its dependencies. Therefore a
var_dump()will possibly dump a very large recursive structure which is impossible to render and read. You have to use
Doctrine\Common\Util\Debug::dump()to restrict the dumping to a human readable level. Additionally you should be aware that dumping the EntityManager to a Browser may take several minutes, and the
Debug::dump()method just ignores any occurrences of it in Proxy instances.
Because we only work with collections for the references we must be careful to implement a bidirectional reference in the domain model. The concept of owning or inverse side of a relation is central to this notion and should always be kept in mind. The following assumptions are made about relations and have to be followed to be able to work with Doctrine 2. These assumptions are not unique to Doctrine 2 but are best practices in handling database relations and Object-Relational Mapping.
- Changes to Collections are saved or updated, when the entity on the owning side of the collection is saved or updated.
- Saving an Entity at the inverse side of a relation never triggers a persist operation to changes to the collection.
- In a one-to-one relation the entity holding the foreign key of the related entity on its own database table is always the owning side of the relation.
- In a many-to-many relation, both sides can be the owning side of the relation. However in a bi-directional many-to-many relation only one is allowed to be.
- In a many-to-one relation the Many-side is the owning side by default, because it holds the foreign key.
- The OneToMany side of a relation is inverse by default, since the foreign key is saved on the Many side. A OneToMany relation can only be the owning side, if its implemented using a ManyToMany relation with join table and restricting the one side to allow only UNIQUE values per database constraint.
Consistency of bi-directional references on the inverse side of a relation have to be managed in userland application code. Doctrine cannot magically update your collections to be consistent.
In the case of Users and Bugs we have references back and forth to the assigned and reported bugs from a user, making this relation bi-directional. We have to change the code to ensure consistency of the bi-directional reference:
I chose to name the inverse methods in past-tense, which should indicate that the actual assigning has already taken place and the methods are only used for **ensuring **consistency of the references. This approach is my personal preference, you can choose whatever method to make this work.
You can see from
User#assignedToBug() that using this method in userland alone would not add the Bug to the collection of the owning side in
Bug#engineer. Using these methods and calling Doctrine for persistence would not update the collections representation in the database.
Bug#setReporter() correctly saves the relation information.
Bug#engineer properties are Many-To-One relations, which point to a User. In a normalized relational model the foreign key is saved on the Bug’s table, hence in our object-relation model the Bug is at the owning side of the relation. You should always make sure that the use-cases of your domain model should drive which side is an inverse or owning one in your Doctrine mapping. In our example, whenever a new bug is saved or an engineer is assigned to the bug, we don’t want to update the User to persist the reference, but the Bug. This is the case with the Bug being at the owning side of the relation.
Bugs reference Products by an uni-directional ManyToMany relation in the database that points from Bugs to Products.
We are now finished with the domain model given the requirements. Lets add metadata mappings for the
Bug as we did for the
<!-- config/xml/Bug.dcm.xml -->
Here we have the entity, id and primitive type definitions. For the “created” field we have used the datetime type, which translates the YYYY-mm-dd HH:mm:ss database format into a PHP DateTime instance and back.
After the field definitions the two qualified references to the user entity are defined. They are created by the many-to-one tag. The class name of the related entity has to be specified with the target-entity attribute, which is enough information for the database mapper to access the foreign-table. Since reporter and engineer are on the owning side of a bi-directional relation we also have to specify the inversed-by attribute. They have to point to the field names on the inverse side of the relationship. We will see in the next example that the inversed-by attribute has a counterpart mapped-by which makes that the inverse side.
The last definition is for the Bug#products collection. It holds all products where the specific bug occurs. Again you have to define the target-entity and field attributes on the many-to-many tag.
The last missing definition is that of the User entity:
<!-- config/xml/User.dcm.xml -->
Here are some new things to mention about the one-to-many tags. Remember that we discussed about the inverse and owning side. Now both reportedBugs and assignedBugs are inverse relations, which means the join details have already been defined on the owning side. Therefore we only have to specify the property on the Bug class that holds the owning sides.
This example has a fair overview of the most basic features of the metadata definition language.
Update your database running:
vendor/bin/doctrine orm:schema-tool:update --force
For starters we need to create user entities:
php create_user.php xiyusullos
We now have the data to create a bug and the code for this scenario may look like this:
Since we only have one user and product, probably with the ID of 1, we can call this script with:
php create_bug.php 1 1 1
Here I got some errors.
$ php create_bug.php 1 1 1
- Carelessly wrote this:
- Should be this:
- Then recall this
vendor/bin/doctrine orm:schema-tool:update --force
This is the first contact with the read API of the EntityManager, showing that a call to
EntityManager#find($name, $id) returns a single instance of an entity queried by primary key. Besides this we see the persist + flush pattern again to save the Bug into the database.
See how simple relating Bug, Reporter, Engineer and Products is done by using the discussed methods in the “A first prototype” section. The UnitOfWork will detect this relationship when flush is called and relate them in the database appropriately.
Using the previous examples we can fill up the database quite a bit, however we now need to discuss how to query the underlying mapper for the required view representations. When opening the application, bugs can be paginated through a list-view, which is the first read-only use-case:
The DQL Query in this example fetches the 30 most recent bugs with their respective engineer and reporter in one single SQL statement. The console output of this script is then:
Somethins does not work! - 11.03.2017
You may wonder why we start writing SQL at the beginning of this use-case. Don’t we use an ORM to get rid of all the endless hand-writing of SQL? Doctrine introduces DQL which is best described as object-query-language and is a dialect of OQL and similar to HQL or JPQL. It does not know the concept of columns and tables, but only those of Entity-Class and property. Using the Metadata we defined before it allows for very short distinctive and powerful queries.
An important reason why DQL is favourable to the Query API of most ORMs is its similarity to SQL. The DQL language allows query constructs that most ORMs don’t: GROUP BY even with HAVING, Sub-selects, Fetch-Joins of nested classes, mixed results with entities and scalar data such as COUNT() results and much more. Using DQL you should seldom come to the point where you want to throw your ORM into the dumpster, because it doesn’t support some the more powerful SQL concepts.
Instead of handwriting DQL you can use the
QueryBuilderretrieved by calling
$entityManager->createQueryBuilder(). There are more details about this in the relevant part of the documentation.
As a last resort you can still use Native SQL and a description of the result set to retrieve entities from the database. DQL boils down to a Native SQL statement and a ResultSetMapping instance itself. Using Native SQL you could even use stored procedures for data retrieval, or make use of advanced non-portable database queries like PostgreSql’s recursive queries.
In the previous use-case we retrieved the results as their respective object instances. We are not limited to retrieving objects only from Doctrine however. For a simple list view like the previous one we only need read access to our entities and can switch the hydration from objects to simple PHP arrays instead.
Hydration can be an expensive process so only retrieving what you need can yield considerable performance benefits for read-only requests.
Implementing the same list view as before using array hydration we can rewrite our code:
There is one significant difference in the DQL query however, we have to add an additional fetch-join for the products connected to a bug. The resulting SQL query for this single select statement is pretty large, however still more efficient to retrieve compared to hydrating objects.
The next Use-Case is displaying a Bug by primary key. This could be done using DQL as in the previous example with a where clause, however there is a convenience method on the EntityManager that handles loading by primary key, which we have already seen in the write scenarios:
The output of the engineer’s name is fetched from the database! What is happening?
Since we only retrieved the bug by primary key both the engineer and reporter are not immediately loaded from the database but are replaced by LazyLoading proxies. These proxies will load behind the scenes, when the first method is called on them.
Sample code of this proxy generated code can be found in the specified Proxy Directory, it looks like:
See how upon each method call the proxy is lazily loaded from the database?
The call prints:
$ php show_bug.php 1
Lazy loading additional data can be very convenient but the additional queries create an overhead. If you know that certain fields will always (or usually) be required by the query then you will get better performance by explicitly retrieving them all in the first query.
For the next use-case we want to retrieve the dashboard view, a list of all open bugs the user reported or was assigned to. This will be achieved using DQL again, this time with some WHERE clauses and usage of bound parameters:
The call prints:
$ php dashboard.php 1
Until now we only retrieved entities or their array representation. Doctrine also supports the retrieval of non-entities through DQL. These values are called “scalar result values” and may even be aggregate values using COUNT, SUM, MIN, MAX or AVG functions.
We will need this knowledge to retrieve the number of open bugs grouped by product:
The call prints:
$ php products.php
There is a single use-case missing from the requirements, Engineers should be able to close a bug. This looks like:
When retrieving the Bug from the database it is inserted into the IdentityMap inside the UnitOfWork of Doctrine. This means your Bug with exactly this id can only exist once during the whole request no matter how often you call
EntityManager#find(). It even detects entities that are hydrated using DQL and are already present in the Identity Map.
When flush is called the EntityManager loops over all the entities in the identity map and performs a comparison between the values originally retrieved from the database and those values the entity currently has. If at least one of these properties is different the entity is scheduled for an UPDATE against the database. Only the changed columns are updated, which offers a pretty good performance improvement compared to updating all the properties.
For now we have not discussed how to separate the Doctrine query logic from your model. In Doctrine 1 there was the concept of
Doctrine_Table instances for this separation. The similar concept in Doctrine2 is called Entity Repositories, integrating the repository pattern at the heart of Doctrine.
Every Entity uses a default repository by default and offers a bunch of convenience methods that you can use to query for instances of that Entity. Take for example our Product entity. If we wanted to Query by name, we can use:
findOneBy() takes an array of fields or association keys and the values to match against.
If you want to find all entities matching a condition you can use
findBy(), for example querying for all closed bugs:
Compared to DQL these query methods are falling short of functionality very fast. Doctrine offers you a convenient way to extend the functionalities of the default
EntityRepository and put all the specialized DQL query logic on it. For this you have to create a subclass of
Doctrine\ORM\EntityRepository, in our case a
BugRepository and group all the previously discussed query functionality in it:
To be able to use this query logic through
$this->getEntityManager()->getRepository('Bug') we have to adjust the metadata slightly.
Now we can remove our query logic in all the places and instead use them through the EntityRepository. As an example here is the code of the first use case “List of Bugs”:
Using EntityRepositories you can avoid coupling your model with specific query logic. You can also re-use query logic easily throughout your application.
count() takes an array of fields or association keys and the values to match against. This provides you with a convenient and lightweight way to count a resultset when you don’t need to deal with it:
This tutorial is over here, I hope you had fun. Additional content will be added to this tutorial incrementally, topics will include:
- More on Association Mappings
- Lifecycle Events triggered in the UnitOfWork
- Ordering of Collections
Additional details on all the topics discussed here can be found in the respective manual chapters.