mirror of
https://github.com/go-gitea/gitea
synced 2024-11-05 01:34:25 +00:00
f891172ef4
This resolves a problem I encountered while updating gitea from 1.20.4 to 1.21. For some reason (correct or otherwise) there are some values in `repository.size` that are NULL in my gitea database which cause this migration to fail due to the NOT NULL constraints. Log snippet (excuse the escape characters) ``` ESC[36mgitea |ESC[0m 2023-12-04T03:52:28.573122395Z 2023/12/04 03:52:28 ...ations/migrations.go:641:Migrate() [I] Migration[263]: Add git_size and lfs_size columns to repository table ESC[36mgitea |ESC[0m 2023-12-04T03:52:28.608705544Z 2023/12/04 03:52:28 routers/common/db.go:36:InitDBEngine() [E] ORM engine initialization attempt #3/10 failed. Error: migrate: migration[263]: Add git_size and lfs_size columns to repository table failed: NOT NULL constraint failed: repository.git_size ``` I assume this should be reasonably safe since `repository.git_size` has a default value of 0 but I don't know if that value being 0 in the odd situation where `repository.size == NULL` has any problematic consequences. |
||
|---|---|---|
| .. | ||
| main_test.go | ||
| v260.go | ||
| v261.go | ||
| v262.go | ||
| v263.go | ||
| v264.go | ||
| v265.go | ||
| v266.go | ||
| v267.go | ||
| v268.go | ||
| v269.go | ||
| v270.go | ||
| v271.go | ||
| v272.go | ||
| v273.go | ||
| v274.go | ||
| v275.go | ||
| v276.go | ||
| v277.go | ||
| v278.go | ||
| v279.go | ||