Skip to content
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

Unable to dump: Failed to dump database: no such column: email_notifications_preference #10207

Closed
1 of 4 tasks
Ghardo opened this issue Feb 10, 2020 · 4 comments
Closed
1 of 4 tasks
Labels
issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail issue/stale

Comments

@Ghardo
Copy link

Ghardo commented Feb 10, 2020

Hello,
i want to backup my gitea data but i get always this error:

Failed to dump database: no such column: email_notifications_preference
git@tools:~$ gitea dump -c /etc/gitea/app.ini
2020/02/10 14:21:35 ...dules/setting/git.go:91:newGit() [I] Git Version: 2.11.0
Failed to dump database: no such column: email_notifications_preference

I have updated my gitea version from 1.9.2

git@tools:~$ gitea -v
Gitea version 1.11.0+rc2-24-g9169b3945 built with GNU Make 4.1, go1.13.7 : bindata, sqlite, sqlite_unlock_notify
  • Gitea version (or commit ref): gitea-1.11-linux-arm-6
  • Git version: 2.11.0
  • Operating system: Raspbian GNU/Linux 9 (stretch) (lite version)
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
@Ghardo
Copy link
Author

Ghardo commented Feb 10, 2020

ok i fixed my problem with the migrate option but the sql contains no data only the structure

@guillep2k
Copy link
Member

guillep2k commented Feb 10, 2020

I think you attempted to dump your database using a 1.10.0+ (edit: actually 1.11.0+rc2) executable before executing the upgrade process, since that column was added in #7813 and did not exist in 1.9.2.

You need to dump your database only with your current version, and then upgrade.

@lunny lunny added the issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail label Feb 11, 2020
@stale
Copy link

stale bot commented Apr 11, 2020

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale stale bot added the issue/stale label Apr 11, 2020
@stale
Copy link

stale bot commented Apr 25, 2020

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail issue/stale
Projects
None yet
Development

No branches or pull requests

3 participants