Closed
Description
- Gitea version (or commit ref): 1.9.6
- Git version: 2.12.3
- Operating system: SuSe Linux Enterprise 12
- Database (use
[x]):- PostgreSQL 9.6.9
- MySQL
- MSSQL
- SQLite
- Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
- Log gist:
Postgres 9.6.9
2019/11/14 17:57:27 ...-xorm/xorm/engine.go:329:Ping() [I] PING DATABASE postgres
2019/11/14 17:57:28 models/models.go:305:NewEngine() [W] Table user Column max_repo_creation db default is '-1'::integer, struct default is -1
2019/11/14 17:57:28 models/models.go:305:NewEngine() [W] Table user Column diff_view_style db default is '''::character varying', struct default is ''
2019/11/14 17:57:28 models/models.go:305:NewEngine() [W] Table user Column theme db default is '''::character varying', struct default is ''
2019/11/14 17:57:28 models/models.go:305:NewEngine() [W] Table webhook Column http_method db default is ''POST'::character varying', struct default is
2019/11/14 17:57:28 models/models.go:305:NewEngine() [W] Table gpg_key column key_id db type is VARCHAR(16), struct type is CHAR(16)
2019/11/14 17:57:28 models/models.go:305:NewEngine() [W] Table gpg_key column primary_key_id db type is VARCHAR(16), struct type is CHAR(16)
2019/11/14 17:57:28 models/models.go:305:NewEngine() [W] Table gpg_key_import column key_id db type is VARCHAR(16), struct type is CHAR(16)
2019/11/14 17:57:28 models/models.go:305:NewEngine() [W] Table commit_status column context_hash db type is VARCHAR(40), struct type is CHAR(40)
2019/11/14 17:57:28 models/models.go:305:NewEngine() [W] Table review column type db type is VARCHAR(255), struct type is INTEGER
2019/11/14 17:57:28 models/models.go:305:NewEngine() [W] Table comment has column old_assignee_id but struct has not related field
2019/11/14 17:57:28 routers/init.go:84:GlobalInit() [I] ORM engine initialization successful!
Description
We get the warnings you can see above this when (re)starting Gitea.
They aren't a result of my update from 1.9.5 to 1.9.6, as some of them were there for a long time, I just haven't come around to open an issue :-)
Is there any way for Gitea to resolve this? Did some migrations not work or does Gitea not do database schema changes?