-
Notifications
You must be signed in to change notification settings - Fork 293
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
Port SqlParameter changes from netcore to netfx #1812
Conversation
@Wraith2 Thanks for the PR. The test pipelines are setup, but there are some adjustments left to be done. I saw some failures on net462 and not sure if you were able to see them. |
It turns out you have to actually set the parameters field so they can be sent to the server or all sorts of things stop working. The CI doesn't seem happy because legs i haven't change (enclave ones) are failing for net6.0 builds. I'm also not sure which ones i should be paying attention to. Do we still have legacy checks? |
I will take the old one out today. The one I was working on, this will be primary one today, is CI-SqlClient-To-Be-Main. |
Most legs are passing but some fail with EXEC(0) |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Codecov ReportBase: 71.38% // Head: 71.39% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #1812 +/- ##
==========================================
+ Coverage 71.38% 71.39% +0.01%
==========================================
Files 290 290
Lines 61236 61265 +29
==========================================
+ Hits 43712 43741 +29
Misses 17524 17524
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Can you kick the CI again please. |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
The failures are odd but appear repeatable. They're in Always Encrypted tests which i have no way to debug locally because of the sql server requirements. I'm going to need some help from the team to investigate why those failures are occuring. As i mentioned in the first post this is a blocking issue for the sql batch api, without these changes there is no way to access the parameter collection for the set of rpc's in the batch. |
The failures don't require Always Encrypted enabled. |
…properties are always set.
…size value and type set.
Ok, all green now. quick merge it before I break it again! |
Ports the changes in SqlParameters perf optimizations to netfx #209.
This is a prerequisite for #19