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

WarningsConfiguration is not propagated correctly in SQL Server provider #29069

Closed
ajcvickers opened this issue Sep 13, 2022 · 0 comments · Fixed by #29086
Closed

WarningsConfiguration is not propagated correctly in SQL Server provider #29069

ajcvickers opened this issue Sep 13, 2022 · 0 comments · Fixed by #29086
Assignees
Labels
area-logging breaking-change closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-bug
Milestone

Comments

@ajcvickers
Copy link
Member

Relational warnings configuration is lost when applying SQL Server-specific warnings.

        coreOptionsExtension = RelationalOptionsExtension.WithDefaultWarningConfiguration(coreOptionsExtension)
            .WithWarningsConfiguration(
                coreOptionsExtension.WarningsConfiguration.TryWithExplicit(
                    SqlServerEventId.ConflictingValueGenerationStrategiesWarning, WarningBehavior.Throw));

Notice that the result of WithDefaultWarningConfiguration is not used to call coreOptionsExtension.WarningsConfiguration.TryWithExplicit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-logging breaking-change closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant