Skip to content

[10.0] Configure row value regression tuple mapping locally - #3960

Merged
roji merged 1 commit into
hotfix/10.0.4from
roji-10-0-row-value-setup
Oct 14, 2026
Merged

roji merged 1 commit into
hotfix/10.0.4from
roji-10-0-row-value-setup

Conversation

@roji

@roji roji commented Oct 14, 2026

Copy link
Copy Markdown
Member

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):

  • Solution build: passed, no warnings or errors.
  • Unit tests: 499 passed, 6 skipped.
  • Isolated AdHocQueryFiltersQueryNpgsqlTest: all 26 passed, including both regression variants; no Northwind tests included.

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
@roji
roji merged commit d11a003 into hotfix/10.0.4 Oct 14, 2026
11 checks passed
@roji
roji deleted the roji-10-0-row-value-setup branch October 14, 2026 20:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

NullReferenceException in shaper for tuple query when a query-filtered entity is reached via both a scalar and collection navigation

1 participant