Giteabot 751028549d Prevent primary key update on migration (#26192) (#26199) ... Backport #26192 by @KN4CK3R Fixes #25918 The migration fails on MSSQL because xorm tries to update the primary key column. xorm prevents this if the column is marked as auto increment: c622cdaf89/internal/statements/update.go (L38-L40) I think it would be better if xorm would check for primary key columns here because updating such columns is bad practice. It looks like if that auto increment check should do the same. fyi @lunny Co-authored-by: KN4CK3R <admin@oldschoolhack.me> (cherry picked from commit ecfbcced46)		2023-07-30 07:46:18 +02:00
..
base	Replace interface{} with any (#25686) (#25687)	2023-07-04 23:41:32 -04:00
fixtures
v1_6	Replace interface{} with any (#25686) (#25687)	2023-07-04 23:41:32 -04:00
v1_7
v1_8	Replace interface{} with any (#25686) (#25687)	2023-07-04 23:41:32 -04:00
v1_9
v1_10	Replace interface{} with any (#25686) (#25687)	2023-07-04 23:41:32 -04:00
v1_11	Fix all possible setting error related storages and added some tests (#23911) (#25244)	2023-06-14 08:36:52 +02:00
v1_12
v1_13
v1_14
v1_15
v1_16	Replace interface{} with any (#25686) (#25687)	2023-07-04 23:41:32 -04:00
v1_17
v1_18
v1_19	Replace interface{} with any (#25686) (#25687)	2023-07-04 23:41:32 -04:00
v1_20	Prevent primary key update on migration (#26192) (#26199)	2023-07-30 07:46:18 +02:00
migrations.go	[BRANDING] Use forgejo binary name	2023-07-17 00:25:56 +02:00