-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Cannot start - tmp_recreate__reaction. Error: Error 1071: Specified key was too long; max key length is 767 bytes #13588
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
Comments
potential (also matches with time frame since error happens) https://github.com/go-gitea/gitea/blob/master/models/migrations/v159.go |
Best solution would be to upgrade mariadb to 10.2.2+ |
It just database limitation and there is not much to do on Gitea side :( |
Checked apt, thats the latest available version on the LTS. Though didn't have any issue with gitea or other applications so far with DB.
Well, use smaller keys? Use small key (numeric id for example) and additional field if required? Potentially then also affects Sqlite |
If you are not going to migrate repositories from other sources you can just alter originalauthor in reactions table to smaller varchar length, that would fix issue for you |
We can't really make it smaller because originalauthor is authors username from external migrated source |
Sqlite does not have such limit imho |
We could probably detect mysql version and use different key for it... |
I have lots of mirrored repos, but simple git-http, no github/gitlab/bitbucket special integration.
Ehm, why use originalauthor even as key? |
Should be able to get around this in older versions with |
No, that's only if you migrate issues or pull requests also
Because when migrating from github we don't have all github users locally in Gitea so we store githubs username beside user id for gitea and we need to limit that there are no duplicate values. We need that for display and also to later be able to associate comments, reactions etc to that user if he authenticates in Gitea using github oauth provider |
I've manually issued create table statement, and aftwards create index with just one field. However, gitea on it's own ignores that and wants to recreate the index still. (no IF NOT EXISTS) @lafriks |
How many times people? Read the FAQ. Use gitea convert |
[x]
):logfile.log
Description
Hello, since about 6 days I cannot start latest version of gitea anymore.
Checked log, and found this in log:
So seemingly some database/orm mapper issue due too big key length.
I have these versions locally from gitea download site (current/master). The latest working version for me is from 10. November, so the bug has been introduced with a commit on/after that day.
The text was updated successfully, but these errors were encountered: