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

Fix for 18063. Add missing concurrency token properties for table splitting #20748

Merged
merged 3 commits into from
Apr 28, 2020

Conversation

lajones
Copy link
Contributor

@lajones lajones commented Apr 25, 2020

Fixes #18063 . Previously if the user was table-splitting and one or more entity types did not map to a concurrency column, we used to throw warning the user to configure the property. Now we simply add it ourselves in shadow state.

@lajones lajones self-assigned this Apr 25, 2020
Added new convention to create a shadow concurrency property on the base-most entity
type(s) in table-splitting scenarios where the property would otherwise be
missing.
@lajones lajones force-pushed the 20200423_Issue18063_01 branch 3 times, most recently from c4d8ca4 to e7f93bf Compare April 27, 2020 21:53

ConventionSet.Remove(
conventionSet.ModelFinalizingConventions,
typeof(TableSharingConcurrencyTokenConvention));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Make this a generic argument

@lajones lajones merged commit 818c93a into master Apr 28, 2020
@lajones lajones deleted the 20200423_Issue18063_01 branch April 28, 2020 06:25
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.

Add missing concurrency token properties for table splitting
2 participants