Skip to content

Conversation

@aaronburtle
Copy link
Contributor

@aaronburtle aaronburtle commented Dec 7, 2022

Why make this change?

Closes #911

What is this change?

In Directory.Packages.Props we update the SQL Client version to 5.0.1

This is the most up to date version, and the current SQL Client version we use is not longer supported.

This creates a large number of namespace collisions in our project with Azure.Operation, most of which are fixed by using Config.Operation instead of Operation.

We tried using Operation = Azure.DataApiBuilder.Config.Operation but this fails to resolve the collisions.

How was this tested?

Ran against existing test suite.

Sample Request(s)

No change to service, can run as normal.

@seantleonard
Copy link
Contributor

If Abhishek's suggestion does not eliminate the need to refactor, make sure to include that information (what you tried, why the refactor is necessary) in your PR description for when you move it out of draft.

@aaronburtle aaronburtle merged commit 688a3a1 into main Dec 9, 2022
@aaronburtle aaronburtle deleted the dev/aaronburtle/UpgradeToSqlClientFive branch December 9, 2022 20:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Consider using a supported version of the SQL Server driver

5 participants