mirror of
https://github.com/go-gitea/gitea.git
synced 2026-07-23 22:04:19 +02:00
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>
25 lines
842 B
Go
25 lines
842 B
Go
// Copyright 2022 The Gitea Authors. All rights reserved.
|
|
// SPDX-License-Identifier: MIT
|
|
|
|
package v1_18
|
|
|
|
import (
|
|
"gitea.dev/modelmigration/base"
|
|
"gitea.dev/modules/timeutil"
|
|
)
|
|
|
|
func AddTeamInviteTable(x base.EngineMigration) error {
|
|
type TeamInvite struct {
|
|
ID int64 `xorm:"pk autoincr"`
|
|
Token string `xorm:"UNIQUE(token) INDEX NOT NULL DEFAULT ''"`
|
|
InviterID int64 `xorm:"NOT NULL DEFAULT 0"`
|
|
OrgID int64 `xorm:"INDEX NOT NULL DEFAULT 0"`
|
|
TeamID int64 `xorm:"UNIQUE(team_mail) INDEX NOT NULL DEFAULT 0"`
|
|
Email string `xorm:"UNIQUE(team_mail) NOT NULL DEFAULT ''"`
|
|
CreatedUnix timeutil.TimeStamp `xorm:"INDEX created"`
|
|
UpdatedUnix timeutil.TimeStamp `xorm:"INDEX updated"`
|
|
}
|
|
|
|
return x.Sync(new(TeamInvite))
|
|
}
|