Cannot Import Dump From Sqlite To Postgres #2923

New Issue

GiteaMirror · 2025-11-02T04:54:15-06:00

GiteaMirror commented

2025-11-02 04:54:15 -06:00

Originally created by @ccaspers on GitHub (Feb 15, 2019).

Gitea version (or commit ref): 3b612ce
Git version: 2.18
Operating system: Linux (using the official Gitea Docker image)
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
Log gist:

Description

I tried migrating a Gitea instance from Sqlite to Postgres. [1] and [2] lead me to believe that this is possible now. What I did:

gitea dump -c /path/to/app.ini -d postgres
Copy the generated gitea-db.sql to my Postgres container
psql -U gitea gitea -f gitea-db.sql inside my container

During the import, a lot of errors were logged to stdout. Here is the collected output: stderr.log

I tried with Postgres 10 and 11. The issue seems to be rooted in the generated sql as CREATE TABLE IF NOT EXISTS "user" ( ... "must_change_password" BOOL DEFAULT 0 NOT NULL ...); causes an error in Postgres. Postgres expects 't' or 'f' for boolean values or requires an explicit cast [3].

[1] https://github.com/go-gitea/gitea/issues/5651
[2] https://github.com/go-gitea/gitea/pull/5680
[3] https://stackoverflow.com/questions/7947814/pgerror-error-column-is-required-is-of-type-boolean-but-expression-is-of-typ

Originally created by @ccaspers on GitHub (Feb 15, 2019).  - Gitea version (or commit ref): 3b612ce - Git version: 2.18 - Operating system: Linux (using the official Gitea Docker image) - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description I tried migrating a Gitea instance from Sqlite to Postgres. [1] and [2] lead me to believe that this is possible now. What I did: 1. `gitea dump -c /path/to/app.ini -d postgres` 2. Copy the generated `gitea-db.sql` to my Postgres container 3. `psql -U gitea gitea -f gitea-db.sql` inside my container During the import, a lot of errors were logged to stdout. Here is the collected output: [stderr.log](https://github.com/go-gitea/gitea/files/2870209/stderr.log) I tried with Postgres 10 and 11. The issue seems to be rooted in the generated sql as `CREATE TABLE IF NOT EXISTS "user" ( ... "must_change_password" BOOL DEFAULT 0 NOT NULL ...);` causes an error in Postgres. Postgres expects `'t'` or `'f'` for boolean values or requires an explicit cast [3]. Related ---------- [1] https://github.com/go-gitea/gitea/issues/5651 [2] https://github.com/go-gitea/gitea/pull/5680 [3] https://stackoverflow.com/questions/7947814/pgerror-error-column-is-required-is-of-type-boolean-but-expression-is-of-typ

GiteaMirror added the issue/stale type/bug labels 2025-11-02 04:54:15 -06:00

GiteaMirror closed this issue

2025-11-02 04:54:16 -06:00

GiteaMirror commented

2025-11-02 04:54:17 -06:00

@lunny commented on GitHub (Mar 27, 2019):

SQLITE store BOOL as INTEGER, so when dump to postgres, it cannot be converted to BOOL because this is only a database to database convert.

@lunny commented on GitHub (Mar 27, 2019): SQLITE store `BOOL` as `INTEGER`, so when dump to postgres, it cannot be converted to `BOOL` because this is only a database to database convert.

GiteaMirror commented

2025-11-02 04:54:17 -06:00

@stale[bot] commented on GitHub (May 26, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (May 26, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 04:54:17 -06:00

@stale[bot] commented on GitHub (Jun 9, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Jun 9, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror referenced this issue

2025-11-02 12:15:53 -06:00

[PR #2923] [MERGED] Update golang x/crypto dependencies #16665

GiteaMirror referenced this issue

2025-11-02 12:16:11 -06:00

[PR #2951] [MERGED] Update golang x/crypto dependencies (#2923) #16678

GiteaMirror referenced this issue