[5.0.1] Fix issues with property called FooId on base type Foo in TPT #23112
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 #23092
Description
The fix does the following:
SqlServerIndexConvention
instead of throwing an exceptionCustomer Impact
Currently when there's property with name in form of FooId on base type named Foo in a TPT hierarchy an exception is thrown when a convention is applied. The workaround is non-obvious and might not work when there are multiple types with this pattern.
How found
Reported by user on RC2
Test coverage
This PR includes tests for the affected scenario.
Regression?
No, this only affects TPT - a new feature in 5.0
Risk
Low. The fix only affects models using TPT.