-
Notifications
You must be signed in to change notification settings - Fork 228
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
Revisit enum/range/extension/composite mapping #1026
Comments
See #2435 (comment) for thoughts on enabling a global opt-in for PG enums and what that would require. We may possibly want to switch to a model which doesn't require up-front mapping at the ADO level. |
roji
added a commit
to roji/efcore.pg
that referenced
this issue
May 12, 2024
Fixes npgsql#2891 Fixes npgsql#3063 Fixes npgsql#1026 Co-authored-by: Nino Floris <mail@ninofloris.com>
roji
added a commit
to roji/efcore.pg
that referenced
this issue
May 13, 2024
Fixes npgsql#2891 Fixes npgsql#3063 Fixes npgsql#1026 Co-authored-by: Nino Floris <mail@ninofloris.com>
roji
added a commit
to roji/efcore.pg
that referenced
this issue
May 13, 2024
Fixes npgsql#2891 Fixes npgsql#3063 Fixes npgsql#1026 Co-authored-by: Nino Floris <mail@ninofloris.com>
roji
added a commit
to roji/efcore.pg
that referenced
this issue
May 17, 2024
Fixes npgsql#2891 Fixes npgsql#3063 Fixes npgsql#1026 Co-authored-by: Nino Floris <mail@ninofloris.com>
roji
added
breaking change
Represents a breaking change
and removed
breaking change
Represents a breaking change
labels
May 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue centralizes mapping design decisions for some advanced PostgreSQL types/objects: enums, user-defined ranges
Current situation
NpgsqlRange<T>
). They have to be defined on the model (for migrations) and in the context options (for NpgsqlTypeMappingSource).Some issues:
Thoughts
The text was updated successfully, but these errors were encountered: