-
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
Basic support for NpgsqlDataSource #2400
Comments
Merged
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With NpgsqlDataSource getting implemented at the ADO.NET layer (npgsql/npgsql#4495), we'll need to react in the EF provider.
As a first basic step, accept an NpgsqlDataSource in UseNpgsql rather than a connection string.
We could also obsolete providing the SSL/TLS callbacks directly on the EF options builder. However, we had a similar ADO discussion about whether to obsolete the SSL/TLS callbacks on NpgsqlConnection, and decided against it for now; we should do the same in EF (i.e. obsolete the EF options builder hooks when we obsolete the NpgsqlConnections ones).
We can also think about improving type mapping customization support (plugins and enums), but that's complex; tracked by #2518 for the future.
The text was updated successfully, but these errors were encountered: