You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we have to use different databases for some entities, depending on some factors. and to not migrate some entities to some databases, we use the following (manually added) in the migration files:
was not sure if i should report this to "dbal" or "migrations" repo, so i reported it to the closest from user perspective.
ps. or if there is an easier way to define "this entity should go only to these connections" or "this entity should never go to these connections", i would love to hear about that!
The text was updated successfully, but these errors were encountered:
Well, as far as DBAL is concerned, connections don't need to have a name. the name is needed to be able to get the connection from a registry. It is not a property of the connection itself (just like the name of a variable containing the connection is not known by the connection).
This means that a Connection object will not give such way to identify itself, and so this bundle will not be able to rely on them to skip migrations
we have to use different databases for some entities, depending on some factors. and to not migrate some entities to some databases, we use the following (manually added) in the migration files:
but this is suboptiomal as that "foobar" is defined in parameters.yml, that the user is supposed to create (like on local devel system).
what would be nicer if we could do:
where "barfoo" is defined in config.yml, that user is not supposed to edit, like:
was not sure if i should report this to "dbal" or "migrations" repo, so i reported it to the closest from user perspective.
ps. or if there is an easier way to define "this entity should go only to these connections" or "this entity should never go to these connections", i would love to hear about that!
The text was updated successfully, but these errors were encountered: