Backport #26192 by @KN4CK3R Fixes #25918 The migration fails on MSSQL because xorm tries to update the primary key column. xorm prevents this if the column is marked as auto increment:c622cdaf89/internal/statements/update.go (L38-L40)
I think it would be better if xorm would check for primary key columns here because updating such columns is bad practice. It looks like if that auto increment check should do the same. fyi @lunny Co-authored-by: KN4CK3R <admin@oldschoolhack.me> (cherry picked from commitecfbcced46
)
This commit is contained in:
parent
5a4b19435d
commit
751028549d
1 changed files with 1 additions and 1 deletions
|
@ -20,7 +20,7 @@ func ChangeContainerMetadataMultiArch(x *xorm.Engine) error {
|
|||
}
|
||||
|
||||
type PackageVersion struct {
|
||||
ID int64 `xorm:"pk"`
|
||||
ID int64 `xorm:"pk autoincr"`
|
||||
MetadataJSON string `xorm:"metadata_json"`
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in a new issue