MapEnum usage not respecting schema boundary

[leonibr]

Hi, thank you in advance for your time reading this issue!

I noticed that specifying a custom schema name on code first migrations and Mapping enums to Postgres in OnModelCreating it generates a script that ignores the informed schema when applying to columns, therefore it is not respecting the schema boundary!

// in a different assembly
namespace Domain {
    public enum TicketStatus {
        NotInformed,
        Opened,
        Closed,
        ReOpened,
        Terminated
    }
}
// => Domain.dll

//DbContext simplified
public class AppDbContext : DbContext
{

    static AppDbContext()
    {
          NpgsqlConnection.GlobalTypeMapper.MapEnum<Domain.TicketStatus>();
     }
    
    protected override void OnModelCreating(ModelBuilder modelBuilder)
     {
                base.OnModelCreating(modelBuilder);
                modelBuilder.HasDefaultSchema(nameof(MyApp));
                modelBuilder.HasPostgresEnum<Domain.TicketStatus>();
                modelBuilder.ToSnakeCase(); <-- lib to format to snake_case, commenting this line does not affect the output.
                //... 
    
    }
}

It generates something like this:

CREATE TYPE myapp.ticket_status AS ENUM ('not_informed', 'opened', 'closed', 're_opened', 'terminated');

ALTER TABLE myapp.ticket_store ALTER COLUMN status TYPE ticket_status;

I believe the expected behavior should be:

ALTER TABLE myapp.ticket_store ALTER COLUMN status TYPE myapp.ticket_status;

(Partial) Workaround:

I solved the problem by adding the search path key into my connection string:

  "ConnectionStrings": {
    "TheMainAppDb": "Database=database;Server=host;User Id=user;Password=******;Search Path=myapp",
    "OtherDb": "..."
  }

This was working fine until I needed a different enum/type in other schema inside the same database...

Thanks

[roji]

Duplicate of #930

[leonibr]

Sorry @roji