Repository navigation
[10.0] Configure row value regression tuple mapping locally - #3960
Merged
Merged
Conversation
Avoid depending on global tuple mapping being enabled before the shared connection pool is initialized. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: cb362e50-f247-4ed7-b24c-6259a9870b3a
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #3954; related to #3933.
Configure record-to-tuple mapping on the regression test's own data source via
ConfigureDataSource, rather than changing the global type mapper inside the test. The global change can happen after inherited tests have initialized the shared pool, causing the regression's sync and async variants to fail depending on test order. This makes the setup independent of other test classes and leaves product code and shared fixtures unchanged.Validation (Release, .NET SDK 10.0.300, PostgreSQL 18.4):
AdHocQueryFiltersQueryNpgsqlTest: all 26 passed, including both regression variants; no Northwind tests included.