From 68e405cf0b00e475c089d8b94cc076d269ab9bb9 Mon Sep 17 00:00:00 2001 From: Giteabot Date: Sun, 2 Jun 2024 15:19:30 +0800 Subject: [PATCH] Fix the possible migration failure on 286 with postgres 16 (#31209) (#31218) Backport #31209 by @lunny Try to fix #31205 Co-authored-by: Lunny Xiao --- models/migrations/v1_22/v286.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/models/migrations/v1_22/v286.go b/models/migrations/v1_22/v286.go index e11d16f8de..6ad669f27c 100644 --- a/models/migrations/v1_22/v286.go +++ b/models/migrations/v1_22/v286.go @@ -92,7 +92,7 @@ func addObjectFormatNameToRepository(x *xorm.Engine) error { // Here to catch weird edge-cases where column constraints above are // not applied by the DB backend - _, err := x.Exec("UPDATE repository set object_format_name = 'sha1' WHERE object_format_name = '' or object_format_name IS NULL") + _, err := x.Exec("UPDATE `repository` set `object_format_name` = 'sha1' WHERE `object_format_name` = '' or `object_format_name` IS NULL") return err }