New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Require separate name and schema in MapEnum #2121

Open
austindrenski opened this Issue Aug 20, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@austindrenski
Member

austindrenski commented Aug 20, 2018

Currently, we have this:

GlobalTypeMapper.MapEnum<SomeEnum>("some_schema.some_enum");

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");
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment