-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
GitHub issue names can be too long and make migrations fail (Postgres/MySQL) #28846
Labels
Comments
Maybe GitHub changed it? |
lunny
pushed a commit
that referenced
this issue
Jan 24, 2024
GiteaBot
pushed a commit
to GiteaBot/gitea
that referenced
this issue
Jan 24, 2024
henrygoodman
pushed a commit
to henrygoodman/gitea
that referenced
this issue
Jan 31, 2024
silverwind
pushed a commit
to silverwind/gitea
that referenced
this issue
Feb 20, 2024
Automatically locked because of our CONTRIBUTING guidelines |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
I tried to migrate the repository https://github.com/tachiyomiorg/tachiyomi with all migration options
The migration always failed at one of the issues with one of these errors:
pq: value too long for type character varying(255)
Error 1406 (22001): Data too long for column 'name' at row 1
Logs from console:
After changing the
name
field type fromcharacter varying(250) NULL
tocharacter varying(1200) NULL
, the migration succeeded.Here is a dump of the
issue
table with the querySELECT * FROM issue WHERE LENGTH(name) > 250;
https://gist.github.com/TristanWasTaken/7cb2c9b2a5c537822796ccb4fc25f513
Issues: tachiyomiorg/tachiyomi#3495, tachiyomiorg/tachiyomi#2337, tachiyomiorg/tachiyomi#4321, tachiyomiorg/tachiyomi#4379, tachiyomiorg/tachiyomi#3897, tachiyomiorg/tachiyomi#4898, tachiyomiorg/tachiyomi#4978, tachiyomiorg/tachiyomi#5066
The migration is still ongoing on the Gitea demo site: https://try.gitea.io/TristanWasTaken/tachiyomi
It'll take ~8h to do a full migration. Or at least that's how long it took on my instance.
Gitea Version
1.21.3
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
Git Version
No response
Operating System
No response
How are you running Gitea?
docker
gitea/gitea:1.21.3
image, withpostgres
andredis
Please note that I also tried with
memory
instead of redis,mysql
(MariaDB) as database and pretty much every variation except sqliteDatabase
PostgreSQL
The text was updated successfully, but these errors were encountered: