Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

"Specified key was too long" when upgrading to 1.5.1 #4949

Closed
2 of 7 tasks
axeloz opened this issue Sep 17, 2018 · 1 comment
Closed
2 of 7 tasks

"Specified key was too long" when upgrading to 1.5.1 #4949

axeloz opened this issue Sep 17, 2018 · 1 comment

Comments

@axeloz
Copy link

axeloz commented Sep 17, 2018

  • Gitea version (or commit ref):
  • Git version: 1.5.1
  • Operating system: Ubuntu 16
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

When upgrading from 1.4.x to 1.5.1, the migration does not seem to work:
2018/09/17 15:35:53 [...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: migrate: do migrate: Sync2: Error 1071: Specified key was too long; max key length is 767 bytes

Thanks
@axeloz
Copy link
Author

axeloz commented Sep 17, 2018

Oooops duplicates #4694

@axeloz axeloz closed this as completed Sep 17, 2018
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@axeloz