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
..
Test_AddCombinedIndexToIssueUser
Test_AddConfidentialClientColumnToOAuth2ApplicationTable	Fix wrong table name (#30557)	2024-04-28 15:39:00 +02:00
Test_AddHeaderAuthorizationEncryptedColWebhook
Test_AddIssueResourceIndexTable
Test_AddPayloadVersionToHookTaskTable
Test_AddRepoIDForAttachment
Test_AddUniqueIndexForProjectIssue	[PORT] gitea#30190: Add unique index for project_issue to prevent duplicate data	2024-04-07 14:51:50 +02:00
Test_CheckProjectColumnsConsistency	Add default board to new projects, remove uncategorized pseudo-board (#29874)	2024-03-30 07:17:31 +01:00
Test_DeleteOrphanedIssueLabels
Test_RemigrateU2FCredentials
Test_RemoveInvalidLabels
Test_RemoveSSHSignaturesFromReleaseNotes
Test_RepositoryFormat	Remove If Exist check on migration for mssql because that syntax required SQL server 2016 (#30894)	2024-05-12 20:03:10 +02:00
Test_StoreWebauthnCredentialIDAsBytes
Test_UnwrapLDAPSourceCfg
Test_UpdateBadgeColName
Test_UpdateOpenMilestoneCounts