With multiple Entity Managers (EM) the Repository uses only the mapped EM for the Entity

[bigs21]

In the manual page How to Work with multiple Entity Managers and Connections for Symfony 4, we can see in the end the following code snippet:

        // Retrieves a repository managed by the "customer" em
        $customers = $this->getDoctrine()
            ->getRepository(Customer::class, 'customer')
            ->findAll()
        ;

Using the ORM configuration code indicated in the beginning of that document, where the Customer entity is mapped to the 'customer' entity manager, the 'customer' parameter for the getRepository() method is ignored.
As so, this last code about repository calls should be updated.

Also, I suggest to add the code on how to use multiple entity managers for a single Entity, or to add a note that it's not possible if that's the case.

[xabbuh]

If this is not working as described, the issue should be reported to the Doctrine issue tracker where the implementing code is located. Though actually I do not see why that should not be working as described.

[bigs21]

Well, after all, it was, as after a few more tests I found out that I had an issue with where the Entities were placed: instead of having them in 'src/Entity/Main' and 'src/Entity/Customer', I had them in 'src/Entity' and 'src/EntityCustomer', with them being configured in that order.

With that, Doctrine was mapping the customer entities to the first (and default) entity manager.

Anyway, from what I've found out that the second parameter to getRepository is currently ignored, as there's no such parameter (is this from a previous version of symfony?).

As so, we can say the following:

        // Retrieves a repository managed by the "customer" em, the Customer's entity em
        $customers = $this->getDoctrine()
            ->getRepository(Customer::class)
            ->findAll()
        ;

        // Retrieves a repository managed by the "customer" em
        $customers = $this->getDoctrine()
            ->getRepository(Customer::class, 'customer')
            ->findAll()
        ;

So, the entity manager used in the repository is always the mapped one of that Entity, and by mapping the entities to a given em, we can't change a different connection to access some Entity, as it will only use the connection for it's em.
That comes from a use case where we were trying to use different connections (different databases) to access the same Entity (the same table structure), but in the same request always use the same connection. For example, depending on some parameter the request would use connection_A or connection_B.

I propose to add a note in the page specifying that it's not possible to use different entity managers to access the same Entity.

[javiereguiluz]

@xabbuh what do you propose to do here? If it's true that getRepository() ignores the second argument ... shouldn't we just remove the second example? Thanks!

[xabbuh]

Yes, I think we shouldn't have it.

[delorie]

Hello,

A brief introduction to our system:
The mission: we want to import data from a MSSQL database into our new application.

We have a vagrantbox, in there running the new application.
And a docker for the MSSQL database.
Now we have an Import Symfony Command Script on hostsystem that connects to the MSSQL database (Docker)
and to the Maria database (Vagrantbox) via SSH 3333:172.0.0.1:3306.

Our Doctrine Config

doctrine:
    dbal:
        default_connection: default
        types:
            uuid_binary_ordered_time: Ramsey\Uuid\Doctrine\UuidBinaryOrderedTimeType
        connections:
            default:
                # configure these for your database server
                driver: 'pdo_mysql'
                [...]
                url: '%env(resolve:DATABASE_URL)%' # Port 3306
                [...]
            command:
                driver: 'pdo_mysql'
                [...]
                url: '%env(resolve:COMMAND_DATABASE_URL)%' # Port 3333
                [...]

    orm:
        auto_generate_proxy_classes: '%kernel.debug%'
        [...]
        default_entity_manager: default
        entity_managers:
            default:
                connection: default
                naming_strategy: doctrine.orm.naming_strategy.underscore
                mappings:
                    App:
                        is_bundle: false
                        type: annotation
                        dir: '%kernel.project_dir%/src/Entity'
                        prefix: 'App\Entity'
                        alias: App
            command:
                connection: command
                naming_strategy: doctrine.orm.naming_strategy.underscore
                mappings:
                    App:
                        is_bundle: false
                        type: annotation
                        dir: '%kernel.project_dir%/src/Entity'
                        prefix: 'App\Entity'
                        alias: AppCommand

In our Command Script:

$doctrine = $this->container->get('doctrine');
$doctrine->getRepository(Salutation::class, 'command')->findAll()

// But Doctrine use the default EntityManager

We found in this File:
vendor/doctrine/persistence/lib/Doctrine/Common/Persistence/AbstractManagerRegistry.php
Doctrine\Common\Persistence\AbstractManagerRegistry

The method "getManagerForClass" ignores the defindet connection
getManagerForClass() (Line: 156)
[...]

foreach ($this->managers as $id) {
    $manager = $this->getService($id);

    if (! $manager->getMetadataFactory()->isTransient($class)) { // <-- first goal 
        return $manager;
    }
}

```php
[...]

// Debug output
$this = {Doctrine\Bundle\DoctrineBundle\Registry} [7]
...
 *Doctrine\Common\Persistence\AbstractManagerRegistry*managers = {array} [2]
  default = "doctrine.orm.default_entity_manager" // <-- first goal 
  command = "doctrine.orm.command_entity_manager"
...


The problem is just by Entitys with defined CustomRepositorys
```php
/**
 * @ORM\Table(name="salutations")
 * @ORM\Entity(repositoryClass="App\Repository\Person\SalutationRepository") // <-- Without CustomRepository it works
 */
class Salutation {}

Without CustomRepository it works because the Method "getRepository" in Class "ContainerRepositoryFactory" found no a $customRepositoryName so the call

return $this->getOrCreateRepository($entityManager, $metadata); (Line 77) // this works finde

but have the method found a CustomRepository the call
$repository = $this->container->get($customRepositoryName);

[pouetman87]

is there any news regarding the resolution of this issue?

[T123mutouren]

关于解决这个问题的消息有什么消息吗？

[andrmoel]

Just don't use a custom repository. This will work.
But IMHO that's no solution. Its a bug, which should be fixed.

[m2payco]

I'm in the same situation. I want to use another entity manager to connect to a read-only replica of the original database using the same entities.

[pouetman87]

the only way that i found to use both custom repositories and more than one database is to use symfony version 3.4

[Floeig]

So far I have found this temporary solution for Symfony4

 private $registry;
    public function __construct(RegistryInterface $registry)
    {
        $this->registry = $registry;
        //parent::__construct($registry, MyEntity::class);
    }

    public function findAllByFieldName($customFieldName, $connection): array
    {
        $em = $this->registry->getEntityManager($connection);

        $customFields = $em->getRepository(MyEntity::class)->findOneBy(['Field_name'=>$customFieldName]);
   /* ...... */
}

Ugly but works..