Provides Doctrine ORM Entity Managers as services to Pimple applications.
- Leverages the core Doctrine Service Provider for either Silex or Cilex.
- Default Entity Manager can be bound to any database connection
- Multiple Entity Managers can be defined
- Mechanism for allowing Service Providers to register their own mappings
- PHP 5.3+
- Doctrine ~2.3
Currently requires both dbs and dbs.event_manager services in order to work. These can be provided by a Doctrine Service Provider like the Silex or Cilex service providers. If you can or want to fake it, go for it. :)
An implementation of dflydev/psr0-resource-locator-service-provider is required if using namespaceish resource mapping. See documentation for orm.generate_psr0_mapping for more information.
Through Composer as dflydev/doctrine-orm-service-provider.
To get up and running, register DoctrineOrmServiceProvider
and
manually specify the directory that will contain the proxies along
with at least one mapping.
In each of these examples an Entity Manager that is bound to the default database connection will be provided. It will be accessible via orm.em.
<?php
// Default entity manager.
$em = $app['orm.em'];
<?php
use Dflydev\Pimple\Provider\DoctrineOrm\DoctrineOrmServiceProvider;
$container = new \Pimple;
$container["db.options"] = array(
"driver" => "pdo_sqlite",
"path" => "/path/to/sqlite.db",
);
// ensure that $container['dbs'] and $container['dbs.event_manager']
// are available, most likely by way of a core service provider.
$container["orm.proxies_dir"] = "/path/to/proxies";
$container["orm.em.options"] = array(
"mappings" => array(
// Using actual filesystem paths
array(
"type" => "annotation",
"namespace" => "Foo\Entities",
"path" => __DIR__."/src/Foo/Entities",
),
array(
"type" => "xml",
"namespace" => "Bat\Entities",
"path" => __DIR__."/src/Bat/Resources/mappings",
),
// Using PSR-0 namespaceish embedded resources
// (requires registering a PSR-0 Resource Locator
// Service Provider)
array(
"type" => "annotation",
"namespace" => "Baz\Entities",
"resources_namespace" => "Baz\Entities",
),
array(
"type" => "xml",
"namespace" => "Bar\Entities",
"resources_namespace" => "Bar\Resources\mappings",
),
),
);
$doctrineOrmServiceProvider = new DoctrineOrmServiceProvider;
$doctrineormServiceProvider->register($container);
<?php
use Dflydev\Silex\Provider\DoctrineOrm\DoctrineOrmServiceProvider;
use Silex\Application;
use Silex\Provider\DoctrineServiceProvider;
$app = new Application;
$app->register(new DoctrineServiceProvider, array(
"db.options" => array(
"driver" => "pdo_sqlite",
"path" => "/path/to/sqlite.db",
),
));
$app->register(new DoctrineOrmServiceProvider, array(
"orm.proxies_dir" => "/path/to/proxies",
"orm.em.options" => array(
"mappings" => array(
// Using actual filesystem paths
array(
"type" => "annotation",
"namespace" => "Foo\Entities",
"path" => __DIR__."/src/Foo/Entities",
),
array(
"type" => "xml",
"namespace" => "Bat\Entities",
"path" => __DIR__."/src/Bat/Resources/mappings",
),
// Using PSR-0 namespaceish embedded resources
// (requires registering a PSR-0 Resource Locator
// Service Provider)
array(
"type" => "annotation",
"namespace" => "Baz\Entities",
"resources_namespace" => "Baz\Entities",
),
array(
"type" => "xml",
"namespace" => "Bar\Entities",
"resources_namespace" => "Bar\Resources\mappings",
),
),
),
));
<?php
use Dflydev\Cilex\Provider\DoctrineOrm\DoctrineOrmServiceProvider;
use Cilex\Application;
use Cilex\Provider\DoctrineServiceProvider;
$app = new Application('My Application');
$app->register(new DoctrineServiceProvider, array(
/** same as the Silex example **/
));
$app->register(new DoctrineOrmServiceProvider, array(
/** same as the Silex example **/
));
-
orm.em.options: Array of Entity Manager options.
These options are available:
-
connection (Default: default): String defining which database connection to use. Used when using named databases via dbs.
-
mappings: Array of mapping definitions.
Each mapping definition should be an array with the following options:
- type: Mapping driver type, one of
annotation
,xml
,yml
orphp
. - namespace: Namespace in which the entities reside.
Additionally, each mapping definition should contain one of the following options:
- path: Path to where the mapping files are located. This should be an actual filesystem path. For the php driver it can be an array of paths
- resources_namespace: A namespaceish path to where the mapping
files are located. Example:
Path\To\Foo\Resources\mappings
Each annotation mapping may also specify the following options:
- use_simple_annotation_reader (Default: true):
If
true
, only simple notations like@Entity
will work. Iffalse
, more advanced notations and aliasing viause
will work. (Example:use Doctrine\ORM\Mapping AS ORM
,@ORM\Entity
) Note that if set tofalse
, theAnnotationRegistry
will probably need to be configured correctly so that it can load your Annotations classes. See this FAQ: Why aren't my Annotations classes being found?
- type: Mapping driver type, one of
-
query_cache (Default: setting specified by orm.default_cache): String or array describing query cache implementation.
-
metadata_cache (Default: setting specified by orm.default_cache): String or array describing metadata cache implementation.
-
result_cache (Default: setting specified by orm.default_cache): String or array describing result cache implementation.
-
-
orm.ems.options: Array of Entity Manager configuration sets indexed by each Entity Manager's name. Each value should look like orm.em.options.
Example configuration:
<?php $app['orm.ems.default'] = 'sqlite'; $app['orm.ems.options'] = array( 'mysql' => array( 'connection' => 'mysql', 'mappings' => array(), ), 'sqlite' => array( 'connection' => 'sqlite', 'mappings' => array(), ), );
Example usage:
<?php $emMysql = $app['orm.ems']['mysql']; $emSqlite = $app['orm.ems']['sqlite'];
-
orm.ems.default (Default: first Entity Manager processed): String defining the name of the default Entity Manager.
-
orm.proxies_dir: String defining path to where Doctrine generated proxies should be located.
-
orm.proxies_namespace (Default: DoctrineProxy): String defining namespace in which Doctrine generated proxies should reside.
-
orm.auto_generate_proxies: Boolean defining whether or not proxies should be generated automatically.
-
orm.default_cache: String or array describing default cache implementation.
-
orm.add_mapping_driver: Function providing the ability to add a mapping driver to an Entity Manager.
These params are available:
- $mappingDriver:
Mapping driver to be added,
instance
Doctrine\Common\Persistence\Mapping\Driver\MappingDriver
. - $namespace:
Namespace to be mapped by
$mappingDriver
, string. - $name:
Name of Entity Manager to add mapping to, string, default
null
.
- $mappingDriver:
Mapping driver to be added,
instance
-
orm.em_name_from_param: Function providing the ability to retrieve an entity manager's name from a param.
This is useful for being able to optionally allow users to specify which entity manager should be configured for a 3rd party service provider but fallback to the default entity manager if not explitely specified.
For example:
<?php $emName = $app['orm.em_name_from_param']('3rdparty.provider.em'); $em = $app['orm.ems'][$emName];
This code should be able to be used inside of a 3rd party service provider safely, whether the user has defined
3rdparty.provider.em
or not. -
orm.generate_psr0_mapping: Leverages dflydev/psr0-resource-locator-service-provider to process a map of namespaceish resource directories to their mapped entities.
Example usage:
<?php $app['orm.ems.config'] = $app->share($app->extend('orm.ems.config', function ($config, $app) { $mapping = $app['orm.generate_psr0_mapping'](array( 'Foo\Resources\mappings' => 'Foo\Entities', 'Bar\Resources\mappings' => 'Bar\Entities', )); $chain = $app['orm.mapping_driver_chain.locator'](); foreach ($mapping as $directory => $namespace) { $driver = new XmlDriver($directory); $chain->addDriver($driver, $namespace); } return $config; }));
- orm.em:
Entity Manager, instance
Doctrine\ORM\EntityManager
. - orm.ems:
Entity Managers, array of
Doctrine\ORM\EntityManager
indexed by name.
When use_simple_annotation_reader is set to False
for an entity,
the AnnotationRegistry
needs to have the project's autoloader added
to it.
Example:
<?php
$loader = require __DIR__ . '/../vendor/autoload.php';
\Doctrine\Common\Annotations\AnnotationRegistry::registerLoader(array($loader, 'loadClass'));
MIT, see LICENSE.
If you have questions or want to help out, join us in the #dflydev or #silex-php channels on irc.freenode.net.
This project is based heavily on both the core Doctrine Service Provider and the work done by @docteurklein on the docteurklein/silex-doctrine-service-providers project. Some inspiration was also taken from Doctrine Bundle and Doctrine Bridge.