Allow specifying connection used by foundry

[BackEndTea]

Currently its not possible to specify the connection that is used by foundry for the inserts.
This is a problem for me as the project i'm working on uses multiple connections, and the default connection may not have
insert rights for the entity i want to persist.

In the flow of the application the correct connection would be used for inserts, but this is not possible to configure for foundry.

Right now we can already specify the connection/entity manger to be used for resets: https://symfony.com/bundles/ZenstruckFoundryBundle/current/index.html#database-reset

However we can't specify the connection that does the inserts. I would like something like

zenstruck_foundry:
   default_entity_manager: my_manager # defaults to doctrine.orm.default_entity_manager

[nikophil]

Hi @BackEndTea

I'm not very familiar with working with multiple entity managers in the same app.

Correct me if I'm wrong: when working with several EM, can you have two EM which "manages" the same entity? In your case one is readonly (the default one), and the other one has write access?

I'd be OK for such a modification, but I'm trying to figure out if a default_entity_manager configuration is the best option 🤔
what if we have 2 databases, with each of them 2 EM, this would not work... Not sure if this is a common setup (I've never seen this in the wild), but I wouldn't want to be stuck if some day someone comes with such a problem

[Norbytus]

I get similar problem, i have two entity manager one for Postgres and another for Clichouse. And its work find with 2em until, you not try to use one entity for both database.

For example next part of symfony orm mapping

    orm:
        default_entity_manager: ~

        auto_generate_proxy_classes: true
        enable_lazy_ghost_objects: true

        entity_managers:
            default:
                connection: default
                naming_strategy: doctrine.orm.naming_strategy.underscore_number_aware
                auto_mapping: true
                mappings:
                    OnlyPostgresEntity:
                        dir: '%kernel.project_dir%/src/Infrastructure/Postgres/Entity'
                        prefix: 'App\Infrastructure\Postgres\Entity'
                    SharedEntity:
                        dir: '%kernel.project_dir%/src/Infrastructure/SharedEntity/Entity'
                        prefix: 'App\Infrastructure\SharedEntity\Entity'
            clickhouse:
                connection: clickhouse
                naming_strategy: doctrine.orm.naming_strategy.underscore_number_aware
                mappings:
                    OnlyClickhouseEntity:
                        dir: '%kernel.project_dir%/src/Infrastructure/ClickHouse/Entity'
                        prefix: 'App\Infrastructure\ClickHouse\Entity'
                    SharedEntity:
                        dir: '%kernel.project_dir%/src/Infrastructure/SharedEntity/Entity'
                        prefix: 'App\Infrastructure\SharedEntity\Entity'

Actually, idk how better resolve things like this). Cause you can have one factory for both connection, and in code it's possibly looks like(kinda ugly)

<?php
 SharedEntityFactory::new()->connection(['default', 'clickhouse'])->createOne();