All primary keys altered in migration after upgrading to 8.0.1

[benjaminoerskov]

After upgrading to 8.0.1, my migrations wants to update all my primary keys like so:

ALTER TABLE `UserPerformanceSettings` MODIFY COLUMN `Id` bigint NOT NULL AUTO_INCREMENT;

The same is true for version 8.0.2. However if I downgrade to version 8.0.0, I no longer get these extra Alters.

Note: I have not changed anything other than the version, and my primary keys are already set like the migration want to change.

Include provider and version information

EF Core version: 8.0.1
Database provider: Pomelo.EntityFrameworkCore.MySql Version="8.0.1
Target framework: NET8.0
Operating system:
IDE: (e.g. Visual Studio 2022 17.8.7)

[ErikEJ]

@benjaminoerskov You should ask in the Pomelo repo, most likely specific for that provider

[roji]

/cc @lauxjpn does this look familiar? Would it be an issue more on your side or on ours?

[lauxjpn]

@roji It is a double post by @benjaminoerskov that we'll handle in PomeloFoundation/Pomelo.EntityFrameworkCore.MySql#1898, since this is a Pomelo specific issue.

Maybe related to this?
#1844

@benjaminoerskov That is correct. As part of #1844, we update the metadata (in the snapshot and <Migration>.Designer.cs file) for all auto_increment columns and for the model itself.

The ALTER TABLE statement should be a noop and not change anything, so you could remove them manually from your Up()/Down() methods if you want to.

I suggest to target 8.0.2 instead of 8.0.1. If fixes some migration related issues.

[roji]

Great, thanks @lauxjpn!

[roji]

Duplicate of PomeloFoundation/Pomelo.EntityFrameworkCore.MySql#1898