Skip to content

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

Merged
ajcvickers merged 1 commit intorelease/7.0from
WotNoShanes0913
Sep 14, 2022
Merged

Ensure warnings configured to throw really do throw with the SQL Server provider#29086
ajcvickers merged 1 commit intorelease/7.0from
WotNoShanes0913

Conversation

@ajcvickers
Copy link
Contributor

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
Contributor 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