Upgrade from 1.8.3 to 1.14.4 : Table project column board_type db type is INT(10) UNSIGNED, struct type is INT UNSIGNED #7571

Closed
opened 2025-11-02 07:30:06 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @ghost on GitHub (Jul 10, 2021).

  • Gitea version (or commit ref):1.14.4
  • Git version:2.17.1
  • Operating system:Ubuntu 18.04.5 LTS
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No

Description

After converting 1.8.3 to 1.14.4, i have succeeded to fix almost problems with :
SET GLOBAL innodb_file_format=Barracuda;
SET GLOBAL innodb_file_per_table=ON;
SET GLOBAL innodb_large_prefix=1;

I do not use docker.
Install and upgrade from binaries gitea (gitea-1.14.4-linux-amd64).

But i always have those two error while trying to run gitea :
2021/07/10 13:03:21 ...rfave/cli/command.go:173:Run() [W] Table project column board_type db type is INT(10) UNSIGNED, struct type is INT UNSIGNED
2021/07/10 13:03:21 ...rfave/cli/command.go:173:Run() [W] Table project column type db type is INT(10) UNSIGNED, struct type is INT UNSIGNED

I tried also a doctor recreate-table everything is fined except for :

2021/07/10 13:14:32 ...rfave/cli/command.go:372:startApp() [W] Table project column board_type db type is INT(10) UNSIGNED, struct type is INT UNSIGNED
2021/07/10 13:14:32 ...rfave/cli/command.go:372:startApp() [W] Table project column type db type is INT(10) UNSIGNED, struct type is INT UNSIGNED

Any help ?

Thanks,
Patrice

Originally created by @ghost on GitHub (Jul 10, 2021). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Make sure it's not mentioned in the FAQ (https://docs.gitea.io/en-us/faq) 5. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref):1.14.4 - Git version:2.17.1 - Operating system:Ubuntu 18.04.5 LTS - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No ## Description After converting 1.8.3 to 1.14.4, i have succeeded to fix almost problems with : SET GLOBAL innodb_file_format=Barracuda; SET GLOBAL innodb_file_per_table=ON; SET GLOBAL innodb_large_prefix=1; I do not use docker. Install and upgrade from binaries gitea (gitea-1.14.4-linux-amd64). But i always have those two error while trying to run gitea : 2021/07/10 13:03:21 ...rfave/cli/command.go:173:Run() [W] Table project column board_type db type is INT(10) UNSIGNED, struct type is INT UNSIGNED 2021/07/10 13:03:21 ...rfave/cli/command.go:173:Run() [W] Table project column type db type is INT(10) UNSIGNED, struct type is INT UNSIGNED I tried also a doctor recreate-table everything is fined except for : 2021/07/10 13:14:32 ...rfave/cli/command.go:372:startApp() [W] Table project column board_type db type is INT(10) UNSIGNED, struct type is INT UNSIGNED 2021/07/10 13:14:32 ...rfave/cli/command.go:372:startApp() [W] Table project column type db type is INT(10) UNSIGNED, struct type is INT UNSIGNED Any help ? Thanks, Patrice
GiteaMirror added the type/question label 2025-11-02 07:30:06 -06:00
Author
Owner

@ghost commented on GitHub (Jul 10, 2021):

Precision : I am using MariaDB Server : 10.1.48-MariaDB-0ubuntu0.18.04.1 - Ubuntu 18.04
Default table type : InnoDB
Default charset : utf8mb4

@ghost commented on GitHub (Jul 10, 2021): Precision : I am using MariaDB Server : 10.1.48-MariaDB-0ubuntu0.18.04.1 - Ubuntu 18.04 Default table type : InnoDB Default charset : utf8mb4
Author
Owner

@zeripath commented on GitHub (Jul 13, 2021):

These warnings can be ignored but if you really want them to disappear, gitea doctor recreate-table project should fix it.

@zeripath commented on GitHub (Jul 13, 2021): These warnings can be ignored but if you really want them to disappear, `gitea doctor recreate-table project` should fix it.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#7571