github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-19 06:32:57 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

migrate local sqllite3 database to MySQL (mariadb) database #6032

New Issue
Closed
opened 2025-11-02 06:43:13 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 06:43:13 -06:00
Owner
Copy Link

Originally created by @TheRojam on GitHub (Sep 20, 2020).

  • Gitea version: 1.12.4
  • Git version: git version 2.24.3
  • Operating system: CentOS Linux release 7.8.2003
  • Database (use [x]):
    • PostgreSQL
    • MySQL (migration target)
    • MSSQL
    • SQLite (base)
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:
    2020/09/20 15:27:33 routers/init.go:86:GlobalInit() [F] ORM engine initialization failed: sync database struct error:
    Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for
    the right syntax to use near 'release MODIFY COLUMN tag_name VARCHAR(255) NULL' at line 1

Description

I would like to migrate my local sqllite3 database to an MySQL (mariadb).
I tried to gitea dump and import the database directly into the mysql database mentioned in the configuration file.
After this my gittea throws 50x errors.

And in the log i can see this error.

2020/09/20 15:27:33 routers/init.go:86:GlobalInit() [F] ORM engine initialization failed: sync database struct error: Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'release MODIFY COLUMN tag_name VARCHAR(255) NULL' at line 1

May i need to mention that i do not have any have such a great knowledge about databases.

Does anyone has an good idea to do this?

Many thanks.

Originally created by @TheRojam on GitHub (Sep 20, 2020). - Gitea version: 1.12.4 - Git version: git version 2.24.3 - Operating system: CentOS Linux release 7.8.2003 - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL (migration target) - [ ] MSSQL - [x] SQLite (base) - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: 2020/09/20 15:27:33 routers/init.go:86:GlobalInit() [F] ORM engine initialization failed: sync database struct error: Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'release MODIFY COLUMN `tag_name` VARCHAR(255) NULL' at line 1 ### Description I would like to migrate my local sqllite3 database to an MySQL (mariadb). I tried to `gitea dump` and import the database directly into the mysql database mentioned in the configuration file. After this my gittea throws 50x errors. And in the log i can see this error. >`2020/09/20 15:27:33 routers/init.go:86:GlobalInit() [F] ORM engine initialization failed: sync database struct error: Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'release MODIFY COLUMN `tag_name` VARCHAR(255) NULL' at line 1` May i need to mention that i do not have any have such a great knowledge about databases. Does anyone has an good idea to do this? Many thanks.
GiteaMirror added the type/question label 2025-11-02 06:43:13 -06:00
GiteaMirror commented 2025-11-02 06:43:13 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Sep 20, 2020):

@TheRojam did you specify he DBMS with the --database flag on dump ?

@6543 commented on GitHub (Sep 20, 2020): @TheRojam did you specify he DBMS with the `--database` flag on **dump** ?
GiteaMirror commented 2025-11-02 06:43:14 -06:00
Author
Owner
Copy Link

@bagasme commented on GitHub (Sep 24, 2020):

@TheRojam Can you post log before your DB error? That means, what is the complete query that trigger the error?

@bagasme commented on GitHub (Sep 24, 2020): @TheRojam Can you post log before your DB error? That means, what is the complete query that trigger the error?
GiteaMirror commented 2025-11-02 06:43:14 -06:00
Author
Owner
Copy Link

@jarvis0325 commented on GitHub (Oct 27, 2020):

FYI
https://inhji.de/blog/migrate-gitea-from-sqlite-to-postgres/

Below is my step list

  1. dump your gitea environment
  2. Use db tool to create new gitea database
  3. Run a new gitea for your new gitea database
  4. check if the tables of your gitea database are auto-create
  5. open your gitea dump sql file
  6. find all insert scripts and then import to gitea database
  7. Fix Sequences which need to begin the max id
  8. change your gitea app.int > database setting to gitea database
@jarvis0325 commented on GitHub (Oct 27, 2020): FYI https://inhji.de/blog/migrate-gitea-from-sqlite-to-postgres/ Below is my step list 1. dump your gitea environment 2. Use db tool to create new gitea database 3. Run a new gitea for your new gitea database 4. check if the tables of your gitea database are auto-create 5. open your gitea dump sql file 6. find all insert scripts and then import to gitea database 7. Fix Sequences which need to begin the max id 8. change your gitea app.int > database setting to gitea database
GiteaMirror commented 2025-11-02 06:43:14 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Mar 22, 2021):

FYI
https://inhji.de/blog/migrate-gitea-from-sqlite-to-postgres/

...

https://web.archive.org/web/20200812160657/https://inhji.de/blog/migrate-gitea-from-sqlite-to-postgres/

@6543 commented on GitHub (Mar 22, 2021): > FYI > https://inhji.de/blog/migrate-gitea-from-sqlite-to-postgres/ > > ... https://web.archive.org/web/20200812160657/https://inhji.de/blog/migrate-gitea-from-sqlite-to-postgres/
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#6032
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?