mirror of
https://github.com/go-gitea/gitea.git
synced 2026-07-23 03:11:22 +02: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>
14 lines
473 B
Go
14 lines
473 B
Go
// Copyright 2022 The Gitea Authors. All rights reserved.
|
|
// SPDX-License-Identifier: MIT
|
|
|
|
package v1_19
|
|
|
|
import "gitea.dev/modelmigration/base"
|
|
|
|
func DropForeignReferenceTable(x base.EngineMigration) error {
|
|
// Drop the table introduced in `v211`, it's considered badly designed and doesn't look like to be used.
|
|
// See: https://github.com/go-gitea/gitea/issues/21086#issuecomment-1318217453
|
|
type ForeignReference struct{}
|
|
return x.DropTables(new(ForeignReference))
|
|
}
|