Maintained
2.10 (upcoming) 2.9.0 (current)
Unmaintained
2.8 2.7 2.6 2.5 2.4 2.3 2.2 2.1 2.0 1.3 1.2 1.1 1.0

Document Repositories

A repository mediates between the domain and data mapping layers using a collection-like interface for accessing domain objects.

In Doctrine, a repository is a class that concentrates code responsible for querying and filtering your documents. ODM provides you with a default DocumentRepository for all of your documents:

1<?php

/* @var $repository \Doctrine\ODM\MongoDB\DocumentRepository */
$repository = $documentManager->getRepository(User::class);
$disabledUsers = $repository->findBy(['disabled' => true, 'activated' => true]);


2


3


4


5

The array passed to findBy specifies the criteria for which documents are matched. ODM will assist with converting PHP values to equivalent BSON types whenever possible:

1<?php
$group = $documentManager->find(Group::class, 123);
/* @var $repository \Doctrine\ODM\MongoDB\DocumentRepository */
$repository = $documentManager->getRepository(User::class);
$usersInGroup = $repository->findBy(['group' => $group]);


2


3


4


5

The default repository implementation provides the following methods:

  • find() - finds one document by its identifier. This may skip a database query

if the document is already managed by ODM. - findAll() - finds all documents in the collection. - findBy() - finds all documents matching the given criteria. Additional query options may be specified (e.g. sort, limit, skip). - findOneBy() - finds one document matching the given criteria. - matching() - Finds all documents matching the given criteria, as expressed with Doctrine's Criteria API.

All above methods will include additional criteria specified by Filters.

Custom Repositories

A custom repository allows filtering logic to be consolidated into a single class instead of spreading it throughout a project. A custom repository class may be specified for a document class like so:

1<?php

namespace Documents;

#[Document(repositoryClass: \Repositories\UserRepository::class)]
class User
{
    /* ... */
}


2


3


4


5


6


7


8


9

The next step is implementing your repository class. In most cases, ODM's default DocumentRepository class may be extended with additional methods that you need. More complex cases that require passing additional dependencies to a custom repository class will be discussed in the next section.

1<?php

namespace Repositories;

class UserRepository extends DocumentRepository
{
    public function findDisabled(): array
    {
        return $this->findBy(['disabled' => true, 'activated' => true]);
    }
}


2


3


4


5


6


7


8


9


10


11

It is also possible to change ODM's default DocumentRepository to your own implementation for all documents (unless overridden by the mapping):

1$documentManager->getConfiguration()
    ->setDefaultRepositoryClassName(MyDefaultRepository::class);


2

Repositories with Additional Dependencies

By default, Doctrine assumes that it can instantiate your repositories in same manner as its default one:

1<?php

namespace Repositories;

use Doctrine\ODM\MongoDB\DocumentRepository;
use Doctrine\ODM\MongoDB\DocumentManager;
use Doctrine\ODM\MongoDB\Mapping\ClassMetadata;
use Doctrine\ODM\MongoDB\UnitOfWork;

class UserRepository extends DocumentRepository
{
    public function __construct(DocumentManager $dm, UnitOfWork $uow, ClassMetadata $classMetadata)
    {
        // The constructor arguments are inherited from DocumentRepository
        parent::__construct($dm, $uow, $classMetadata);
    }
}


2


3


4


5


6


7


8


9


10


11


12


13


14


15


16


17

In order to change the way Doctrine instantiates repositories, you will need to implement your own RepositoryFactory

In the following example, we create a custom repository factory to pass Symfony's event dispatcher to the repository constructor.

1<?php

use Doctrine\ODM\MongoDB\DocumentRepository;
use Doctrine\ODM\MongoDB\DocumentManager;
use Doctrine\ODM\MongoDB\Mapping\ClassMetadata;
use Doctrine\ODM\MongoDB\Repository\AbstractRepositoryFactory;
use Doctrine\ODM\MongoDB\UnitOfWork;
use Symfony\Component\EventDispatcher\EventDispatcherInterface;

final class YourRepositoryFactory extends AbstractRepositoryFactory
{
    public function __construct(
        private EventDispatcherInterface $eventDispatcher,
    ) {
    }

    protected function instantiateRepository(string $repositoryClassName, DocumentManager $documentManager, ClassMetadata $metadata)
    {
        return match ($repositoryClassName) {
            UserRepository::class => new UserRepository($this->eventDispatcher, $documentManager, $metadata),
            default               => new $repositoryClassName($documentManager, $documentManager->getUnitOfWork(), $metadata),
        };
    }
}


2


3


4


5


6


7


8


9


10


11


12


13


14


15


16


17


18


19


20


21


22


23


24

The factory class must then be registered in the Configuration:

1<?php

$eventDispatcher = $container->get('event_dispatcher');
$repoFactory = new YourRepositoryFactory($eventDispatcher);
$configuration = new Configuration();
// your other config here
$configuration->setRepositoryFactory($repoFactory);


2


3


4


5


6


7