-
Notifications
You must be signed in to change notification settings - Fork 286
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
Standardize Connection String properties for enhanced user experience #534
Conversation
5c0dd5e
to
16155da
Compare
@cheenamalhotra |
Thanks for trying out and capturing the issue, our tests covered this property but was limited to connection string builder, hence this got missed. #585 will fix this issue. Thanks! |
…strings see dotnet/SqlClient#1780 and dotnet/SqlClient#534 Application Intent (previously ApplicationIntent) Connect Retry Count (previously ConnectRetryCount) Connect Retry Interval (previously ConnectRetryInterval) Pool Blocking Period (previously PoolBlockingPeriod) Multiple Active Result Sets (previously MultipleActiveResultSets) Multiple Subnet Failover (previously MultiSubnetFailover) Transparent Network IP Resolution (previously TransparentNetworkIPResolution) Trust Server Certificate (previously TrustServerCertificate)
This change introduced huge compat issues. System.Data.Client does not understand connection strings generated by Microsoft.Data.Client. |
Some connection string properties are breaking the theme of connection string properties for SqlClient and end users need to track which connection string properties are spelled differently. This change standardizes the connection properties for better user experience.
The below connection properties are now updated with synonyms created for backwards compatibility:
ApplicationIntent
)ConnectRetryCount
)ConnectRetryInterval
)PoolBlockingPeriod
)MultipleActiveResultSets
)MultiSubnetFailover
)TransparentNetworkIPResolution
)TrustServerCertificate
)P.S. Also made some improvements on documentation.