Context
Issue #288 requested adding ADO.Net synonyms to connection string parameters. PR #368 addresses the minimum ask (authentication synonym + spaced auth value names), but the broader set of ADO.Net SqlClient synonyms remain unsupported.
Current State
The adoSynonyms map in msdsn/conn_str.go currently has:
| Synonym |
Maps to |
application name |
app name |
data source, address, network address, addr |
server |
user, uid |
user id |
pwd |
password |
initial catalog |
database |
column encryption setting |
columnencryption |
authentication (PR #368) |
fedauth |
Missing ADO.Net Synonyms
These are common ADO.Net SqlClient connection string keywords that users migrating from .NET would expect to work:
| ADO.Net Keyword |
Should map to (driver key) |
connect timeout |
connection timeout |
integrated security / trusted_connection |
integrated auth flag (needs design) |
failover partner (spaced) |
failoverpartner |
application intent (spaced) |
applicationintent |
trust server certificate (spaced) |
trustservercertificate |
multi subnet failover (spaced) |
multisubnetfailover |
hostname in certificate (spaced) |
hostnameincertificate |
current language |
TBD (if supported) |
wsid |
workstation id |
Some of these are simple spelling/spacing variants of existing keys. Others (like integrated security / trusted_connection) may need additional design since they map to a boolean concept rather than a direct key.
References
Context
Issue #288 requested adding ADO.Net synonyms to connection string parameters. PR #368 addresses the minimum ask (authentication synonym + spaced auth value names), but the broader set of ADO.Net SqlClient synonyms remain unsupported.
Current State
The
adoSynonymsmap inmsdsn/conn_str.gocurrently has:application nameapp namedata source,address,network address,addrserveruser,uiduser idpwdpasswordinitial catalogdatabasecolumn encryption settingcolumnencryptionauthentication(PR #368)fedauthMissing ADO.Net Synonyms
These are common ADO.Net
SqlClientconnection string keywords that users migrating from .NET would expect to work:connect timeoutconnection timeoutintegrated security/trusted_connectionfailover partner(spaced)failoverpartnerapplication intent(spaced)applicationintenttrust server certificate(spaced)trustservercertificatemulti subnet failover(spaced)multisubnetfailoverhostname in certificate(spaced)hostnameincertificatecurrent languagewsidworkstation idSome of these are simple spelling/spacing variants of existing keys. Others (like
integrated security/trusted_connection) may need additional design since they map to a boolean concept rather than a direct key.References