Skip to content
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

Merged
merged 2 commits into from
May 20, 2020

Conversation

cheenamalhotra
Copy link
Member

@cheenamalhotra cheenamalhotra commented Apr 20, 2020

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:

  • 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)

P.S. Also made some improvements on documentation.

@cheenamalhotra cheenamalhotra added the 🆕 Public API Issues/PRs that introduce new APIs to the driver. label Apr 20, 2020
@cheenamalhotra cheenamalhotra merged commit 47f918a into dotnet:master May 20, 2020
@jeremy-waguet
Copy link

jeremy-waguet commented Jun 1, 2020

@cheenamalhotra
This PR supposed to be backward compatible with the non spaced names but on my project ApplicationIntent=ReadWrite produces an 'unknown keyword exception applicationintent' whereas Application Intent=ReadWrite work !?? The other multi-word properties appears to work (I am using only TrustServerCertificate +MultiSubnetFailover)

@cheenamalhotra
Copy link
Member Author

Hi @jeremy-waguet

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!

majorsilence added a commit to TownSuite/TownSuite.MultiTenant that referenced this pull request Aug 29, 2023
…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)
@VladimirKhvostov
Copy link

This change introduced huge compat issues. System.Data.Client does not understand connection strings generated by Microsoft.Data.Client.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🆕 Public API Issues/PRs that introduce new APIs to the driver.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants