Change schemas.Column to use int64 #2160

Merged
lunny merged 4 commits from zeripath/xorm:length-as-int64 into master 2022-07-14 05:55:24 +00:00

4 Commits

Author SHA1 Message Date
1f504c6518
come on drone 2
All checks were successful
continuous-integration/drone/pr Build is passing
Signed-off-by: Andrew Thornton <art27@cantab.net>
2022-07-13 21:19:13 +01:00
f34f97d15b
come on drone
Some checks failed
continuous-integration/drone/pr Build is failing
Signed-off-by: Andrew Thornton <art27@cantab.net>
2022-07-13 20:58:30 +01:00
9278b05d7e
fix test
Some checks failed
continuous-integration/drone/pr Build is failing
Signed-off-by: Andrew Thornton <art27@cantab.net>
2022-07-13 20:28:39 +01:00
72bfadeefd
Change schemas.Column to use int64
Some checks failed
continuous-integration/drone/pr Build is failing
The largest size of a column in SQL is above the largest integer that
can be stored in an int/int32. Running go on a 32bit machine will result
in ints being mapped to int32 and thus interpretting the schema will
fail.

In this PR we change the schema.Column to use int64 which will allow
Gitea to fix https://github.com/go-gitea/gitea/issues/20161

Signed-off-by: Andrew Thornton <art27@cantab.net>
2022-07-12 18:52:03 +01:00