Skip to content
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

Ensure warnings configured to throw really do throw with the SQL Server provider #29086

Merged
merged 1 commit into from
Sep 14, 2022

Conversation

ajcvickers
Copy link
Member

Note that this is a breaking change because this bug was preventing exceptions being thrown when they should have been.

Fixes #29069

@ajcvickers
Copy link
Member Author

@roji @lauxjpn It might be worth checking your code if you have any default "warnings as errors" specific to your providers.

Copy link
Member

@AndriySvyryd AndriySvyryd left a comment

Choose a reason for hiding this comment

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

Such a subtle change

@ajcvickers ajcvickers merged commit 26163b2 into release/7.0 Sep 14, 2022
@ajcvickers ajcvickers deleted the WotNoShanes0913 branch September 14, 2022 19:23
@roji
Copy link
Member

roji commented Sep 14, 2022

Oh wow, yeah... I had to stare at that for a couple minutes before I saw it... In fact I wouldn't trust myself not to refactor that back :) Good thing there are tests.

roji added a commit to npgsql/efcore.pg that referenced this pull request Sep 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

WarningsConfiguration is not propagated correctly in SQL Server provider
3 participants