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

Migrations: Honor [Column(Order)] in CreateTable operation #25942

Merged
merged 1 commit into from
Sep 13, 2021

Conversation

bricelam
Copy link
Contributor

@bricelam bricelam commented Sep 8, 2021

Resolves #10059

@bricelam bricelam requested a review from a team September 8, 2021 20:20
@bricelam
Copy link
Contributor Author

bricelam commented Sep 8, 2021

Since SQLite does a table rebuild for any AlterColumn operation, we end up doing a full rebuild if you change the explicit order of a column, so that actually works on SQLite. 😁

@ghost
Copy link

ghost commented Sep 10, 2021

Hello @bricelam!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

@ghost
Copy link

ghost commented Sep 10, 2021

Apologies, while this PR appears ready to be merged, I've been configured to only merge when all checks have explicitly passed. The following integrations have not reported any progress on their checks and are blocking auto-merge:

  1. Azure Pipelines

These integrations are possibly never going to report a check, and unblocking auto-merge likely requires a human being to update my configuration to exempt these integrations from requiring a passing check.

Give feedback on this
From the bot dev team

We've tried to tune the bot such that it posts a comment like this only when auto-merge is blocked for exceptional, non-intuitive reasons. When the bot's auto-merge capability is properly configured, auto-merge should operate as you would intuitively expect and you should not see any spurious comments.

Please reach out to us at [email protected] to provide feedback if you believe you're seeing this comment appear spuriously. Please note that we usually are unable to update your bot configuration on your team's behalf, but we're happy to help you identify your bot admin.

@ghost
Copy link

ghost commented Sep 11, 2021

Apologies, while this PR appears ready to be merged, it looks like release/6.0 is a protected branch and I have not been granted permission to perform the merge.

@bricelam bricelam merged commit 637b9a2 into dotnet:release/6.0 Sep 13, 2021
@bricelam bricelam deleted the order branch September 13, 2021 16:15
Comment on lines +248 to +251
if (operation[RelationalAnnotationNames.ColumnOrder] != operation.OldColumn[RelationalAnnotationNames.ColumnOrder])
{
Dependencies.MigrationsLogger.ColumnOrderIgnoredWarning(operation);
}
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Providers, you may also want to add this code to your AlterColumn code. (and AddColumn if you don't call base)

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.

Allow defining column order via [ColumnAttribute.Order] when creating tables
2 participants