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 to #25013 - Outstanding work for temporal tables #25563

Merged
merged 1 commit into from
Aug 18, 2021

Conversation

maumar
Copy link
Contributor

@maumar maumar commented Aug 18, 2021

Removing unnecessary temporal annotations on runtime entity types, also avoiding adding EnsureSchemaOperation if the schema that is to be created has already been added in the migration batch.

Assert.Equal("mySchema", orders[SqlServerAnnotationNames.TemporalHistoryTableSchema]);
});

// TODO: we could avoid creating the schema if we peek into the model
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm thinking that looking into the model seems like too much work. Keeping the test in case we change our mind (or do disagree already and think we should do it?)

@AndriySvyryd
Copy link
Member

You need to switch the target branch if you want this to go into rc1

@ajcvickers
Copy link
Contributor

+1 to put this in rc1

@maumar maumar changed the base branch from main to release/6.0-rc1 August 18, 2021 20:49
Removing unnecessary temporal annotations on runtime entity types, also avoiding adding EnsureSchemaOperation if the schema that is to be created has already been added in the migration batch.
@maumar maumar merged commit 7186a58 into release/6.0-rc1 Aug 18, 2021
@maumar maumar deleted the fix25013_rc1 branch August 18, 2021 21:14
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.

3 participants