Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Merge | SqlInternalConnectionTds preparation#3323

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation

edwardneal
Copy link
Contributor

This contains the preparatory work for the merge of SqlInternalConnectionTds. We're working with a smaller code file here, so I've merged every part of the two files which avoids a behavioural change.

This should be easier to review comment-by-comment - it's bulky, but not complex. I'd also appreciate a CI run.

At the end of this, the diff is +43/-80. Remaining differences here are:

  • Optimisation: netcore will clear the array of session state when the connection resets, netfx will replace it with a new array.
  • netfx will consider four extra error codes from the server to be transient: 40020, 40143, 40166, 40540.
  • netfx contains a little context connection support.
  • netfx contains support for Transparent Network IP Resolution, while netcore does not.
  • netfx supports the Network Library connection string parameter.
  • netcore will throw an exception if it receives an ENV_LOGSHIPNODE ENVCHANGE when the connection string's Application Intent is read-only, while netfx will not.
  • When getting the federated authentication token, netfx will stop retrying if the next pause between each attempt to acquire a token would cause the connection timeout to be expired.
  • netcore supports passing the User ID parameter to MSAL as an initial username; netfx does not.
  • Some exception messages are more precise in netfx than they are in netcore.

What should we do with Transparent Network IP Resolution? This functionality doesn't exist in netcore at all - does it need to be ported? If it only exists in netfx for backwards compatibility, should it be made obsolete?

I'd also be interested to know what the right style of exception messages is. If (for example) the connection receives an unexpected session recovery feature extension acknowledgement, which exception message should I merge in favour of?

Internal connection fatal error. Error state: {ParsingErrorState}, Feature Id: {ID of feature}.

Internal connection fatal error.

The former is netfx, the latter is netcore. I prefer the detail of netfx, but I imagine netcore changed this for a reason.

…perty.netcore: synced explicit variable type in declaration.
@benrr101
Copy link
Contributor

/azp run

@azure-pipelinesAzure Pipelines
Copy link

Azure Pipelines successfully started running 2 pipeline(s).

Copy link
Contributor

@benrr101benrr101 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Looks pretty good to me, my only comments are probably out of scope since the overall goal is to align the two codebases, not necessarily clean them up. Feel free to address or ignore and comment on my comments.

@benrr101benrr101 added the Common Project 🚮Things that relate to the common project project labelMay 5, 2025
@benrr101benrr101 added this to the6.1-preview2 milestoneMay 5, 2025
@codecovCodecov
Copy link

codecovbot commentedMay 5, 2025
edited
Loading

Codecov Report

Attention: Patch coverage is65.05376% with65 lines in your changes missing coverage. Please review.

Project coverage is 62.15%. Comparing base(08622e7) to head(9fda691).
Report is 24 commits behind head on main.

Files with missing linesPatch %Lines
...crosoft/Data/SqlClient/SqlInternalConnectionTds.cs45.00%33 Missing⚠️
...crosoft/Data/SqlClient/SqlInternalConnectionTds.cs74.19%32 Missing⚠️

❗ There is a different number of reports uploaded between BASE (08622e7) and HEAD (9fda691). Click for more details.

HEAD has 1 upload less than BASE
FlagBASE (08622e7)HEAD (9fda691)
addons10
Additional details and impacted files
@@             Coverage Diff             @@##             main    #3323       +/-   ##===========================================- Coverage   75.42%   62.15%   -13.28%===========================================  Files         262      292       +30       Lines       41241    65263    +24022     ===========================================+ Hits        31106    40562     +9456- Misses      10135    24701    +14566
FlagCoverage Δ
addons?
netcore66.50% <45.90%> (-8.80%)⬇️
netfx60.62% <74.40%> (?)

Flags with carried forward coverage won't be shown.Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report?Share it here.

🚀 New features to boost your workflow:
  • ❄️Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Contributor

@benrr101benrr101 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Thanks for looking at the comments - looking forward to getting this merged 🚀 🚢

@benrr101
Copy link
Contributor

/azp run

@azure-pipelinesAzure Pipelines
Copy link

Azure Pipelines successfully started running 2 pipeline(s).

@benrr101benrr101 merged commitdc1298a intodotnet:mainMay 16, 2025
237 checks passed
@edwardnealedwardneal deleted the merge/sqlinternalconnectiontds-preparation branchMay 16, 2025 16:55
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@benrr101benrr101benrr101 approved these changes

@paulmedynskipaulmedynskipaulmedynski approved these changes

Assignees
No one assigned
Labels
Common Project 🚮Things that relate to the common project project
Projects
None yet
Milestone
6.1-preview2
Development

Successfully merging this pull request may close these issues.

3 participants
@edwardneal@benrr101@paulmedynski

[8]ページ先頭

©2009-2025 Movatter.jp