Get access to actual connection for migration

In my case I need add some specific settings in Migration file. migrationBuilder.Sql(sqlcode)

If I correctly understand all operation in migration uses MasterConnection (postgres database). https://github.com/npgsql/Npgsql.EntityFrameworkCore.PostgreSQL/blob/8e97e4195b197ae3d16763704352acfffa95c73f/src/EFCore.PG/Storage/Internal/NpgsqlDatabaseCreator.cs#L41

But for my settings I need actual connection to actual database. Can I somehow get access to connection. Maybe I can inherit from NpgsqlDatabaseCreator and use connection directly https://github.com/npgsql/Npgsql.EntityFrameworkCore.PostgreSQL/blob/8e97e4195b197ae3d16763704352acfffa95c73f/src/EFCore.PG/Storage/Internal/NpgsqlDatabaseCreator.cs#L22

Maybe there are other ways?

[westfin]

I’m sorry I really was wrong. Raw SQL work fine.

My problem was in custom NpgsqlMigrationsSqlGenerator. I tryed reimplement Generate method to append some sql commands: https://github.com/npgsql/Npgsql.EntityFrameworkCore.PostgreSQL/blob/89b9742df7bebab9bdc92f259bb6ecf66da30365/src/EFCore.PG/Migrations/NpgsqlMigrationsSqlGenerator.cs#L601

I was inattentive. @roji @austindrenski Thank you for help.

[roji]

I’m probably misunderstanding something here, but the master connection is only used to create the database. The rest of the migration code - table creation and any additional raw SQL - happens on the regular connection to the database. So any ALTER DATABASE statement you specify in raw SQL should actually work fine. Can you please double-check and provide more detail?

Aside from that, we do support specifying the tablespace on the database, mainly because this is an option that must be specified in CREATE DATABASE and cannot be altered later. We can support other database creation (and alteration) options as needed, but anything that can be altered later should be easily doable with raw SQL.