Download the PHP package roave/psr-container-doctrine without Composer

psr-container-doctrine: Doctrine Factories for PSR-11 Containers

Doctrine factories for PSR-11 containers.

This package provides a set of factories to be used with containers using the PSR-11 standard for an easy Doctrine integration in a project. This project was originally written by @DASPRiD but maintenance has been taken over by Roave.

Installation

The easiest way to install this package is through composer:

Configuration

In the general case where you are only using a single connection, it's enough to define the entity manager factory:

If you want to add a second connection, or use another name than "orm_default", you can do so by using the static variants of the factories:

You can also define an alias to retrieve an entity manager instance using ::class capability:

Each factory supplied by this package will by default look for a registered factory in the container. If it cannot find one, it will automatically pull its dependencies from on-the-fly created factories. This saves you the hassle of registering factories in your container which you may not need at all. Of course, you can always register those factories when required. The following additional factories are available:

• (doctrine.cache.*)
• (doctrine.connection.*)
• (doctrine.configuration.*)
• (doctrine.driver.*)
• (doctrine.event_manager.*)

Each of those factories supports the same static behavior as the entity manager factory. For container specific configurations, there are a few examples provided in the example directory:

• Aura.Di
• PimpleInterop
• Laminas\ServiceManager

Example configuration

A complete example configuration can be found in example/full-config.php. Please note that the values in there are the defaults, and don't have to be supplied when you are not changing them. Keep your own configuration as minimal as possible. A minimal configuration can be found in example/minimal-config.php

Migrations

If you want to expose the migration commands, you have to map the command name to CommandFactory. This factory needs migrations config setup. For ExecuteCommand example:

You can find a full list of available commands in example/full-config.php.

Using the Doctrine CLI

In order to be able to use the CLI tool of Doctrine, you need to create a file in your project directory. This sets up the command line application and enables you to add custom commands. It's nearly identical to the file described in Setting Up the Console but pulls EntityManagerInterface from your container:

After that, invoke to see the available commands.

Multiple connections

It gets a little trickier when you have multiple entity managers. Doctrine itself has no way to handle that itself, so a possible way would be to have two copies of the command above, named after the manager they work with and each pulling different entity managers from the container - for instance and .

The following code can be used for multiple connections, but it has a drawback: you won't see the --em=... option within the help section of each command.

Multiple connections and migrations

There may be a requirement for a migration table in each connection. Whether its a different database entirely, or other another schema (PostgreSQL for example).

For this to work you must first ensure the service \Doctrine\Migrations\Configuration\Migration\ConfigurationLoader is not set in the container. This allows for the factory \Roave\PsrContainerDoctrine\Migrations\DependencyFactoryFactory to create its own ConfigurationLoader by the key provided.

You first need to add additional config to the migrations in the doctrine config

Now the example bin/doctrine script above can be extended to use the $em variable along with the CommandFactory.