SqlServer Migrations: Rebuild primary keys when column collation changes

Open
#26,115 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp, sql
Domain
database

Research direction

Start by examining the Microsoft.EntityFrameworkCore.SqlServer migration provider and reproduce the reported failure when a key column's collation changes. The work is done when the migration can alter the collation without the primary key dependency error and the affected migration behavior is covered by a regression test.

Written by the indexing model from the issue text.

Description

area-migrations area-sqlserver customer-reported

File a bug

Migrating a column collation fails when the column is used as a key, with the error:

System.Data.SqlClient.SqlException (0x80131904): The object 'PK_[object]' is dependent on column '[column]'.
ALTER TABLE ALTER COLUMN [column] failed because one or more objects access this column.

EF Core version: 5.0.9
Database provider: Microsoft.EntityFrameworkCore.SqlServer
Target framework: .NET Core 3.1
Operating system: Windows

Dominant language
C#
Stars
14.8k
Forks
3.4k
Avg merge
2d 5h
Merged PRs (30d)
134

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/efcore

All issues in dotnet/efcore

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.