Lunny Xiao 32c97efab4 Remove If Exist check on migration for mssql because that syntax required SQL server 2016 (#30894) ... Fix #30872 We will assume the database is consistent before executing the migration. So the indexes should exist. Removing `IF EXIST` then is safe enough. --------- Co-authored-by: silverwind <me@silverwind.io> (cherry picked from commit 40de54ece82356b161cdb9cc224ed9004af8ae5d) Conflicts: models/migrations/v1_22/v286.go MSSQL is not supported in Forgejo		2024-05-12 20:03:10 +02:00
..
main_test.go
v280.go
v281.go
v282.go
v283.go	[CHORE] Remove Microsoft SQL Server Support	2024-04-05 23:37:36 +02:00
v283_test.go
v284.go
v285.go
v286.go	[CHORE] Remove Microsoft SQL Server Support	2024-04-05 23:37:36 +02:00
v286_test.go	Remove If Exist check on migration for mssql because that syntax required SQL server 2016 (#30894)	2024-05-12 20:03:10 +02:00
v287.go
v288.go
v289.go
v290.go
v290_test.go
v291.go
v292.go
v293.go
v293_test.go
v294.go	Rename migration package name for 1.22-rc1 (#30730)	2024-04-28 15:39:01 +02:00
v294_test.go	Rename migration package name for 1.22-rc1 (#30730)	2024-04-28 15:39:01 +02:00
v295.go	Rename migration package name for 1.22-rc1 (#30730)	2024-04-28 15:39:01 +02:00
v296.go	Rename migration package name for 1.22-rc1 (#30730)	2024-04-28 15:39:01 +02:00
v298.go	Rename migration package name for 1.22-rc1 (#30730)	2024-04-28 15:39:01 +02:00