d18464fd58
- Use setting.Database.Type.IsSQLite3() / IsMySQL() for dialect checks to match the rest of models/migrations/. - Trim the migration's comment to the load-bearing why (MSSQL rejects inline DEFAULT, MySQL drops it on MODIFY COLUMN), drop the discovery narrative. - Trim test comments and tighten the type-name assertion list to the values dialects actually emit (verified empirically against the CI image versions: MySQL/MSSQL report "INT", Postgres reports "INTEGER"; "INT4" never surfaces, removed). Re-tested against postgres:14, bitnamilegacy/mysql:8.0, mssql:2019-latest, and SQLite — all pass. Co-Authored-By: Claude (Opus 4.7) <noreply@anthropic.com>
39 lines
1.2 KiB
Go
39 lines
1.2 KiB
Go
// Copyright 2026 The Gitea Authors. All rights reserved.
|
|
// SPDX-License-Identifier: MIT
|
|
|
|
package v1_27
|
|
|
|
import (
|
|
"code.gitea.io/gitea/models/migrations/base"
|
|
"code.gitea.io/gitea/modules/setting"
|
|
|
|
"xorm.io/xorm"
|
|
"xorm.io/xorm/schemas"
|
|
)
|
|
|
|
// WidenProjectBoardSorting changes project_board.sorting from int8 to int so the
|
|
// API can stop truncating sort values and the column count is no longer capped at
|
|
// 127. DefaultIsEmpty: true is required because MSSQL's ALTER COLUMN rejects an
|
|
// inline DEFAULT, and MySQL's MODIFY COLUMN drops any DEFAULT not restated, so the
|
|
// default is reapplied for MySQL afterwards. Postgres and MSSQL keep the existing
|
|
// DEFAULT constraint independently of the type change.
|
|
func WidenProjectBoardSorting(x *xorm.Engine) error {
|
|
if setting.Database.Type.IsSQLite3() {
|
|
return nil
|
|
}
|
|
if err := base.ModifyColumn(x, "project_board", &schemas.Column{
|
|
Name: "sorting",
|
|
SQLType: schemas.SQLType{Name: "INT"},
|
|
Nullable: false,
|
|
DefaultIsEmpty: true,
|
|
}); err != nil {
|
|
return err
|
|
}
|
|
if setting.Database.Type.IsMySQL() {
|
|
if _, err := x.Exec("ALTER TABLE `project_board` ALTER `sorting` SET DEFAULT 0"); err != nil {
|
|
return err
|
|
}
|
|
}
|
|
return nil
|
|
}
|