diff options
author | 6543 <6543@obermui.de> | 2022-07-14 20:40:30 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-07-14 19:40:30 +0100 |
commit | 181814952779c92942d296647852a5a3aa394c79 (patch) | |
tree | d490ba99b1974f2f81158c68254662b3049bb209 /go.mod | |
parent | 931c02d1521b7b990f70a590c691b066dbc27d4d (diff) | |
download | gitea-181814952779c92942d296647852a5a3aa394c79.tar.gz gitea-181814952779c92942d296647852a5a3aa394c79.zip |
update xorm.io/xorm v1.3.2-0.20220714055524-c3bce556200f (#20371)
Xorm 1.3.2-0.20220714055524 contains a fix for interpreting db column sizes. Prior to this fix xorm would assume that the size of a column was within the range of an `int`. This is correct on 64bit machines where `int` is typical equivalent to `int64` however, on 32bit machines `int` tends to be `int32`.
Unfortunately the size of a LONGTEXT field is actually `max_uint32`, thus using `strconv.Atoi` on these fields will fail and thus #20161 occurs on 32 bit arm. Xorm 1.3.2-0.20220714055524 changes this field to use int64 instead.
Fix #20161
Diffstat (limited to 'go.mod')
-rw-r--r-- | go.mod | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -104,7 +104,7 @@ require ( mvdan.cc/xurls/v2 v2.4.0 strk.kbt.io/projects/go/libravatar v0.0.0-20191008002943-06d1c002b251 xorm.io/builder v0.3.11 - xorm.io/xorm v1.3.1 + xorm.io/xorm v1.3.2-0.20220714055524-c3bce556200f ) require ( |