Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Require separate name and schema in MapEnum #2121
Currently, we have this:
Which contributes to the issues in the EF Core provider involving default schemas and detecting when to escape user defined type names.
npgsql/Npgsql.EntityFrameworkCore.PostgreSQL#605 attempts to address this from the provider-side, but it would be better if the type mapping treated names and schema's separately:
GlobalTypeMapper.MapEnum<SomeEnum>(name: "some_enum", schema: "some_schema");