I added a column to the primary key, but the automatic migration did not take effect.

befor

type ComicViewLog struct {
    FileName            string    `json:"fileName"`
    LastViewComicId     string    `gorm:"primaryKey;autoIncrement:false" json:"lastViewComicId"`
    FilePath            string    `json:"filePath"`
}

after

type ComicViewLog struct {
    FileName            string    `gorm:"primaryKey;autoIncrement:false" json:"fileName"`
    LastViewComicId     string    `gorm:"primaryKey;autoIncrement:false" json:"lastViewComicId"`
    FilePath            string    `json:"filePath"`
}

do

db.AutoMigrate(&PkzComicViewLog{})

The primary key remains only LastViewComicId

Comment From: niuhuan

Onconflict cannot be used if the primary key is not migrated. I want Gorm to manage all migration actions

Comment From: github-actions[bot]

The issue has been automatically marked as stale as it missing playground pull request link, which is important to help others understand your issue effectively and make sure the issue hasn't been fixed on latest master, checkout https://github.com/go-gorm/playground for details. it will be closed in 30 days if no further activity occurs. if you are asking question, please use the Question template, most likely your question already answered https://github.com/go-gorm/gorm/issues or described in the document https://gorm.io ✨ Search Before Asking

Comment From: salimane

@niuhuan have you resolved this ?

Comment From: niuhuan

@niuhuan have you resolved this ?

I don't remember, manual operation ? Or upgrade gorm?