gitea/models/migrations/v1_20
KN4CK3R 7866a6e0e2
Prevent primary key update on migration (#26192)
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
2023-07-28 09:54:31 +02:00
..
main_test.go Redesign Scoped Access Tokens (#24767) 2023-06-04 20:57:16 +02:00
v244.go
v245.go
v246.go
v247.go
v248.go
v249.go
v250.go Prevent primary key update on migration (#26192) 2023-07-28 09:54:31 +02:00
v251.go
v252.go Fix admin team access mode value in team_unit table (#24012) 2023-04-13 21:06:10 +02:00
v253.go Add migration to fix external unit access mode of owner/admin team (#24117) 2023-04-15 09:52:44 -04:00
v254.go Support upload `outputs` and use `needs` context on Actions (#24230) 2023-04-22 16:12:41 -04:00
v255.go Display when a repo was archived (#22664) 2023-04-26 10:46:26 -04:00
v256.go Add Debian package registry (#24426) 2023-05-02 12:31:35 -04:00
v257.go Implement actions artifacts (#22738) 2023-05-19 21:37:57 +08:00
v258.go Add the ability to pin Issues (#24406) 2023-05-25 15:17:19 +02:00
v259.go Redesign Scoped Access Tokens (#24767) 2023-06-04 20:57:16 +02:00
v259_test.go Redesign Scoped Access Tokens (#24767) 2023-06-04 20:57:16 +02:00