Closed zijchen closed 2 years ago
Why the change from tedious to go-sqlcmd?
Also, what situations were ClientId/TenantId required for? Were they supported before, and we're just making it explicit, or are they supported in some other way?
Why the change from tedious to go-sqlcmd?
Also, what situations were ClientId/TenantId required for? Were they supported before, and we're just making it explicit, or are they supported in some other way?
The current implementation (v1) utilizes sqlcmd, and through that it supports substituting sqlcmd variables into the scripts. While changing to tedious simplified the support for various AAD auth types with script execution, it broke the variable substitution capabilities of sqlcmd. Go-sqlcmd combines support for AAD auth types and sqlcmd variables
Fixes #119
Initial implementation of v2 used the tedious driver to test connection to database. For some reason their driver requires tenant-id and client-id to be explicitly set. However with go-sqlcmd implementation, this is no longer necessary.