All primary keys altered in migration after upgrading efcore to 8.0.1 about pomelo.entityframeworkcore.mysql HOT 3 CLOSED

So does that mean, if I only have these changes in my migration, I can completely remove the migration, and only commit a changed snapshot?

Yes, that should usually work.

from pomelo.entityframeworkcore.mysql.

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.

from pomelo.entityframeworkcore.mysql.

@lauxjpn Thank you for your response, and I'm sorry I made a duplicate issue.

So does that mean, if I only have these changes in my migration, I can completely remove the migration, and only commit a changed snapshot?

I am currently targeting 8.0.2, I just noticed the issue started at 8.0.1 :)

from pomelo.entityframeworkcore.mysql.