Migrate database from sqlite3 to mysql

[ChristmasZCY]

Feature Description

Hi!
The database I used at the beginning was sqlite3 because it was easy to deploy. As my databases increased, the original sqlite3 files became larger and larger, and the speed also became slower. I hope to migrate to mysql, but I don't know how to migrate. Is there a built-in tool?

Screenshots

No response

[Linjieqiang]

Converting one database type to another is not a well-tested process and you may experience issues. It is better to choose the final database type at the type of the first installation. Be aware that SQLite does not scale; if you expect your instance to grow at a later time, you should choose another database type.

[ChristmasZCY]

Thank you, sounds so sad.

Converting one database type to another is not a well-tested process and you may experience issues. It is better to choose the final database type at the type of the first installation. Be aware that SQLite does not scale; if you expect your instance to grow at a later time, you should choose another database type.

[MelvinCou]

It is possible, see https://docs.gitea.com/administration/backup-and-restore#using-gitea-dump-to-convert-database-types
But as said above, that's at your own risk

Or using raw sqlite dump features : https://stackoverflow.com/questions/18671/quick-easy-way-to-migrate-sqlite3-to-mysql

[juleslagarde]

@ChristmasZCY I'm curious. Using Gitea with SQLite, where did you see slowdowns ? Do you think, it's linked to the number of repos ? How many repos do you have ?

[softengel]

@ChristmasZCY Maybe solve SQLite issues and then consider to migrate...

Some commands are your friend:
SQLITE_TMPDIR=. sqlite3 gitea.db VACUUM;
sqlite3 gitea.db "SELECT name ,SUM(pgsize)/1024 table_size FROM "dbstat" GROUP BY name ORDER BY table_size desc;" | less

For example if action is to big (app.ini):
[cron.delete_old_actions]
ENABLED = true
RUN_AT_START = true
NOTICE_ON_SUCCESS = true
SCHEDULE = @every 24h
OLDER_THAN = 144h

Better to migrate as less as possible.
And gitea will be much faster with small sqlite3 db.

[ChristmasZCY]

Sometimes, when I open a repo in web, It loads slow. As follows.
There is 3717 repos in my web.
The gitea.db file is 2.2G.

@ChristmasZCY I'm curious. Using Gitea with SQLite, where did you see slowdowns ? Do you think, it's linked to the number of repos ? How many repos do you have ?我很好奇。将 Gitea 与 SQLite 一起使用，您在哪里看到速度变慢？你认为，它与 repos 的数量有关吗？您有多少个存储库 ？

[ChristmasZCY]

Thank you, I'll try it.

@ChristmasZCY Maybe solve SQLite issues and then consider to migrate...也许解决 SQLite 问题，然后考虑迁移......

Some commands are your friend:有些命令是你的朋友： SQLITE_TMPDIR=. sqlite3 gitea.db VACUUM;SQLITE_TMPDIR=。sqlite3 gitea.db 真空; sqlite3 gitea.db "SELECT name ,SUM(pgsize)/1024 table_size FROM "dbstat" GROUP BY name ORDER BY table_size desc;" | lesssqlite3 gitea.db “SELECT name ，SUM（pgsize）/1024 table_size FROM ”dbstat“ GROUP BY name ORDER BY table_size desc;” |少

For example if action is to big (app.ini):例如，如果 action 是 to big （app.ini）： [cron.delete_old_actions] ENABLED = true  启用 = true RUN_AT_START = true  RUN_AT_START = 真 NOTICE_ON_SUCCESS = trueNOTICE_ON_SUCCESS = 真 SCHEDULE = @every 24h  时间表 = 24 小时 OLDER_THAN = 144h  OLDER_THAN = 144 小时

Better to migrate as less as possible.最好尽可能少地迁移。 And gitea will be much faster with small sqlite3 db.而 gitea 在小 sqlite3 db 时会快得多。

It is possible, see https://docs.gitea.com/administration/backup-and-restore#using-gitea-dump-to-convert-database-types这是可能的，请参阅 https://docs.gitea.com/administration/backup-and-restore#using-gitea-dump-to-convert-database-types But as said above, that's at your own risk但如上所述，这是您自己承担的风险

Or using raw sqlite dump features : https://stackoverflow.com/questions/18671/quick-easy-way-to-migrate-sqlite3-to-mysql或使用原始 sqlite 转储功能：https://stackoverflow.com/questions/18671/quick-easy-way-to-migrate-sqlite3-to-mysql