Configurate doctrine_migration_versions table in custom schema instead of public

Question

Is there a way for the automatic doctrine_migration_versionsto be stored in a schema other than public?

Right now I have a schema called inschrijving and all the entities properties are stored as tables and columns within that schema, but not the doctrine migration versions table.

Here's how my entities are stored:

And the doctrine_migration_versions is stored in the public schema:

I cannot find anywhere how to configure doctrine in order for the doctrine_migration_versions to be stored within the inschrijving schema instead of the public schema

score 5 · Accepted Answer · answered Jan 18 '22 at 13:58

5

Found it myself by asking in another forum, but if anyone is interested:

doctrine_migrations:
    storage:
        # Default (SQL table) metadata storage configuration
        table_storage:
            table_name: 'inschrijving.doctrine_migration_versions'

You will need to create the schema manually in the db before applying migrations, though.

CREATE SCHEMA inschrijving;

And then

php bin/console doctrine:migrations:migrate

And it should look like this:

answered Jan 18 '22 at 13:58

Ari

388
1
5
21

1

Nice find @Ari! But, independently of this, does it make sense to keep these two separated? – Jovan Perovic Jan 22 '22 at 15:02
@JovanPerovic thanks, wdym with "these two" seperated? – Ari Jan 24 '22 at 11:14
I mean for tables to be in one schema and migrations data in another? – Jovan Perovic Jan 24 '22 at 13:48
1

@JovanPerovic no it doesn't make sense, but that's why I asked the question – Ari Jan 26 '22 at 11:29

Configurate doctrine_migration_versions table in custom schema instead of public

1 Answers1