[release/9.0] Use the correct comparer when sorting relational functions. #34712
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.
Fixes #34672
Description
The implementation of
IRelationalModel.Functions
didn't specify a comparer and the default fails when trying to compare two instances. This regressed in d8e9f61Customer impact
When a model contains more than one function that returns the same entity type an exception is thrown in validation. There is no known workaround.
How found
Reported by user on 9.0.0-rc1.
Regression
Yes. From 8.0.x
Testing
Test added.
Risk
Low.