New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
option --em does nothing for me #507
Comments
I find a way to make it work with --configuration I move config/packages/doctrine_migrations_bordereau.yaml to root of my project => /doctrine_migrations_bordereau.yaml then I remove
And this commande works:
So I can use : But I think it would be usefull to not have a configuration file that is not in package and it would be great to have abilities to configure migrations path for specifics entityManager. |
Hello,
I use "doctrine/doctrine-migrations-bundle": "3.2.4" in a Symfony project with two databases.
Here is my configuration:
Project work perfect, but I have executed query on database without migration bundle. And I would like to reset this important functionality.
First question : how it can detect which migrations directory go with which entityManager ?
It is ok when I execute command
bin/console doctrine:m:diff -v --em=bordereau
but it put a file in '%kernel.project_dir%/migrations/gli-agrement' while I would like to get it inbordereau
directory.Then when I execute
bin/console doctrine:m:m -v --em=bordereau
it try to play '%kernel.project_dir%/migrations/gli-agrement' migrations in my bordereau database.I didn't find the way to associate migrations to an entityManager. The config doc doesn't explain how to configure that. I suppose we should have something like it was specified here : #364 (comment)
Something missing here : https://symfony.com/doc/current/doctrine/multiple_entity_managers.html
And here too : https://symfony.com/bundles/DoctrineMigrationsBundle/current/index.html
about multiple connections.
I have tried another way:
with this config :
But I get this error :
Migrations configuration key "doctrine_migrations" does not exist.
which is mentioned in this thread #341 and should have been fixed since 2020. So I don't understandMany thanks in advance for your help.
The text was updated successfully, but these errors were encountered: