Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release/5.0] Preserve the null table mapping in migration snapshot when an entity type is used as a TVF return type. #25175

Merged
merged 1 commit into from Jul 6, 2021

Conversation

AndriySvyryd
Copy link
Member

@AndriySvyryd AndriySvyryd commented Jun 29, 2021

Fixes #25133

Part of a larger fix from 6.0: 6b4ee13

Description

When an entity type is used as a TVF return type the (lack of) table mapping is not preserved in the model snapshot.

Customer Impact

This causes a migration to be generated even without any model changes. And the generated migration produces an error when applied.
Anyone using TVFs (a new feature in 5.0) is affected by this unless they do want to map the entity type to a table.

How found

Reported by a customer.

Test coverage

Test coverage for this case has been added in this PR.

Regression?

No.

Risk

Low. The change only affect design-time tooling that generate source code. No quirk as it's unfeasible to turn it on when using the tools.

@dougbu dougbu merged commit 595974e into release/5.0 Jul 6, 2021
@dougbu dougbu deleted the Issue25133 branch July 6, 2021 22:10
@dougbu dougbu added this to the 5.0.x milestone Oct 5, 2021
@smitpatel smitpatel removed this from the 5.0.x milestone May 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants