-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
DB topic.name uses varying(25) which makes mirrors of repos with long topics fail #14108
Comments
We need index the column, so it shouldn't too big. How many characters with Github Topic name? 🤔 |
The one it fails with is 26, but I think it would be fine to just drop topics that are too long on migration. Gitea shouldn't fail just because of it though. What do you think? |
@michaelx Good idea! We need a PR to fix that. |
PR is up for grabs as this isn't my stack, I am afraid. Thanks. |
it certainly appears that there is no limit in GH |
I confirm that error:
Is it an typo ? All other ALTER TABLE `topic` CHANGE `name` `name` VARCHAR(255); After that migration was successfull |
it's partly to do with the fact that they're indexed but I suspect it's an incorrect decision and we should just increase that field and either make it be indexed with bleve or just deal with it. |
I didn't provide pull request cause i don't know right final solution. It was only dirty hotfix. I'm looking forward fixed version. |
Please note: NOT ONLY POSTGRES |
In which Gitea version it will be fixed? |
A simple solution is to change to a big size i.e. 50 , but that may also not enough? |
docker-compose
with the imagegitea/gitea:1
Description
https://github.com/survivejs/webpack-book
as a mirrorCan be solved by using
varying(255)
ontopic.name
. Is there a reason it's limited to 25?The text was updated successfully, but these errors were encountered: