mirror of
https://github.com/go-gitea/gitea.git
synced 2026-07-22 17:02:41 +00:00
fff32e9469
Migrations should never use model structs directly, because the model structs can be different in different releases. e.g. if one migration uses "User" model, it works in the early releases, then one day, when the User model changes, the migration breaks because it will use the new (incorrect) User model, it should only use the old User model. The same to "modules/structs". --------- Signed-off-by: wxiaoguang <wxiaoguang@gmail.com> Co-authored-by: delvh <dev.lh@web.de>
36 lines
635 B
YAML
36 lines
635 B
YAML
# type IssueLabel struct {
|
|
# ID int64 `xorm:"pk autoincr"`
|
|
# IssueID int64 `xorm:"UNIQUE(s)"`
|
|
# LabelID int64 `xorm:"UNIQUE(s)"`
|
|
# }
|
|
-
|
|
id: 1 # Should remain - matches comment 2
|
|
issue_id: 1
|
|
label_id: 1
|
|
should_remain: true
|
|
-
|
|
id: 2 # Should remain
|
|
issue_id: 2
|
|
label_id: 2
|
|
should_remain: true
|
|
-
|
|
id: 3 # Should be deleted
|
|
issue_id: 1
|
|
label_id: 3
|
|
should_remain: false
|
|
-
|
|
id: 4 # Should remain
|
|
issue_id: 3
|
|
label_id: 1
|
|
should_remain: true
|
|
-
|
|
id: 5 # Should be deleted
|
|
issue_id: 3
|
|
label_id: 2
|
|
should_remain: false
|
|
-
|
|
id: 6 # Should be deleted
|
|
issue_id: 3
|
|
label_id: 5
|
|
should_remain: false
|