Repository navigation
[8.0] Fix type mapping for derived tsquery parameters - #4061
Merged
Merged
Conversation
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
1 participant
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.
Backport #4058 to
hotfix/8.0.12.Registers the seven built-in
NpgsqlTsQuerysubclasses with the existingtsquerymapping, leaving generic type-mapping lookup and SQL translation unchanged. Preserves the mapping regression coverage and adapts the sync/asyncMatchesregression to the 8.0 branch's existing Northwind full-text fixture.Validated with the branch-pinned .NET 8 SDK: 96 mapping tests and 61 full-text tests passed against isolated PostgreSQL 16 (one existing full-text test skipped).
The separate empty-tsquery serialization issue #886 is not addressed.
Fixes #3041