github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 11:37:49 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #2464] Table 'vikunja.database_notification' doesn't exist #6679

New Issue
Closed
opened 2026-04-20 17:16:04 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-20 17:16:04 -05:00
Owner
Copy Link

Originally created by @urmel1960 on GitHub (Mar 24, 2026).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2464

Pre-submission checklist

  • I have searched for existing open or closed issue reports with the same problem.

Description

The vikunja dump command fails with a database error referencing a non-existent table database_notification.

# docker exec vikunja /app/vikunja/vikunja dump -p /app/vikunja/files/
2026/03/24 07:00:19 failed to create modcache index dir: mkdir /.cache: permission denied
time=2026-03-24T07:00:19.411Z level=INFO msg="Using config file: /etc/vikunja/config.yml"
time=2026-03-24T07:00:19.412Z level=INFO msg="Running migrations…"
time=2026-03-24T07:00:19.442Z level=INFO msg="Ran all migrations successfully."
time=2026-03-24T07:00:19.465Z level=INFO msg="Start dumping config file..."
time=2026-03-24T07:00:19.466Z level=INFO msg="Dumped config file"
time=2026-03-24T07:00:19.467Z level=INFO msg="Dumped .env file"
time=2026-03-24T07:00:19.467Z level=INFO msg="Start dumping version file..."
time=2026-03-24T07:00:19.467Z level=INFO msg="Dumped version"
time=2026-03-24T07:00:19.467Z level=INFO msg="Start dumping database..."
time=2026-03-24T07:00:19.467Z level=ERROR msg="error saving database data: Error 1146 (42S02): Table 'vikunja.database_notification' doesn't exist"

Analysis

The dump command references a table called database_notification, but the actual table in the database is named notifications:

mysql> SHOW TABLES LIKE '%notification%';
+-----------------------------------+
| Tables_in_vikunja (%notification%)|
+-----------------------------------+
| notifications                     |
+-----------------------------------+

mysql> SHOW TABLES LIKE '%database%';
Empty set (0.00 sec)

The notifications table exists and has the expected structure:

CREATE TABLE `notifications` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `notifiable_id` bigint(20) NOT NULL,
  `notification` text NOT NULL,
  `name` varchar(250) NOT NULL,
  `subject_id` bigint(20) DEFAULT NULL,
  `read_at` datetime DEFAULT NULL,
  `created` datetime NOT NULL,
  PRIMARY KEY (`id`),
  ...
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4

Environment

  • Vikunja version: v2.2.2
  • Database: MariaDB 10 (Docker container)
  • Deployment: Docker (official vikunja/vikunja image)
  • Installation: Fresh install ~3 weeks ago (started with v2.0)
  • Upgrades: v2.0 → v2.1 (few days ago) → v2.2.2 (today)
  • Note: Migrations report "Ran all migrations successfully" but the migration table shows last entry from February 2026. Possibly not all v2.1/v2.2 migrations were recorded or required.

Concern regarding migrations

While Vikunja reports "Ran all migrations successfully" on every startup, the migration table shows the last recorded entry from February 2026. After upgrading from v2.0 → v2.1 → v2.2.2, I would expect to see new migration entries — but there are none.

This raises concerns:

  1. Are migrations actually running, or is the success message misleading?
  2. Could there be silent migration failures that don't get recorded?
  3. Is the mismatch between the table name in code (database_notification) and the actual schema (notifications) a symptom of incomplete migrations?

Expected behavior

vikunja dump should successfully export the database, referencing the correct table name notifications.

Workaround

Manual backup via mysqldump works without issues:

docker exec vikunja-db mysqldump -u vikunja -p'***' vikunja > backup.sql

Vikunja Version

v2.2.2

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Please select

Screenshots

No response

Originally created by @urmel1960 on GitHub (Mar 24, 2026). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2464 ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same problem. ### Description The `vikunja dump` command fails with a database error referencing a non-existent table `database_notification`. ``` # docker exec vikunja /app/vikunja/vikunja dump -p /app/vikunja/files/ 2026/03/24 07:00:19 failed to create modcache index dir: mkdir /.cache: permission denied time=2026-03-24T07:00:19.411Z level=INFO msg="Using config file: /etc/vikunja/config.yml" time=2026-03-24T07:00:19.412Z level=INFO msg="Running migrations…" time=2026-03-24T07:00:19.442Z level=INFO msg="Ran all migrations successfully." time=2026-03-24T07:00:19.465Z level=INFO msg="Start dumping config file..." time=2026-03-24T07:00:19.466Z level=INFO msg="Dumped config file" time=2026-03-24T07:00:19.467Z level=INFO msg="Dumped .env file" time=2026-03-24T07:00:19.467Z level=INFO msg="Start dumping version file..." time=2026-03-24T07:00:19.467Z level=INFO msg="Dumped version" time=2026-03-24T07:00:19.467Z level=INFO msg="Start dumping database..." time=2026-03-24T07:00:19.467Z level=ERROR msg="error saving database data: Error 1146 (42S02): Table 'vikunja.database_notification' doesn't exist" ``` ### Analysis The dump command references a table called `database_notification`, but the actual table in the database is named `notifications`: ```sql mysql> SHOW TABLES LIKE '%notification%'; +-----------------------------------+ | Tables_in_vikunja (%notification%)| +-----------------------------------+ | notifications | +-----------------------------------+ mysql> SHOW TABLES LIKE '%database%'; Empty set (0.00 sec) ``` The `notifications` table exists and has the expected structure: ```sql CREATE TABLE `notifications` ( `id` bigint(20) NOT NULL AUTO_INCREMENT, `notifiable_id` bigint(20) NOT NULL, `notification` text NOT NULL, `name` varchar(250) NOT NULL, `subject_id` bigint(20) DEFAULT NULL, `read_at` datetime DEFAULT NULL, `created` datetime NOT NULL, PRIMARY KEY (`id`), ... ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 ``` ### Environment - **Vikunja version:** v2.2.2 - **Database:** MariaDB 10 (Docker container) - **Deployment:** Docker (official vikunja/vikunja image) - **Installation:** Fresh install ~3 weeks ago (started with v2.0) - **Upgrades:** v2.0 → v2.1 (few days ago) → v2.2.2 (today) - **Note:** Migrations report "Ran all migrations successfully" but the `migration` table shows last entry from February 2026. Possibly not all v2.1/v2.2 migrations were recorded or required. ### Concern regarding migrations While Vikunja reports "Ran all migrations successfully" on every startup, the `migration` table shows the last recorded entry from February 2026. After upgrading from v2.0 → v2.1 → v2.2.2, I would expect to see new migration entries — but there are none. This raises concerns: 1. Are migrations actually running, or is the success message misleading? 2. Could there be silent migration failures that don't get recorded? 3. Is the mismatch between the table name in code (`database_notification`) and the actual schema (`notifications`) a symptom of incomplete migrations? ### Expected behavior `vikunja dump` should successfully export the database, referencing the correct table name `notifications`. ### Workaround Manual backup via mysqldump works without issues: ```bash docker exec vikunja-db mysqldump -u vikunja -p'***' vikunja > backup.sql ``` ### Vikunja Version v2.2.2 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Please select ### Screenshots _No response_
GiteaMirror commented 2026-04-20 17:16:06 -05:00
Author
Owner
Copy Link

@vikunja-bot-app[bot] commented on GitHub (Mar 24, 2026):

This issue has been fixed in #2469, please check with the next unstable build (should be ready for deployment in ~30min, also on the demo).

<!-- gh-comment-id:4119344417 --> @vikunja-bot-app[bot] commented on GitHub (Mar 24, 2026): This issue has been fixed in #2469, please check with the next unstable build (should be ready for deployment in ~30min, also on [the demo](https://try.vikunja.io)).
GiteaMirror commented 2026-04-20 17:16:06 -05:00
Author
Owner
Copy Link

@urmel1960 commented on GitHub (Mar 24, 2026):

How can I deploy an unstable buidl with my docker installation ?

<!-- gh-comment-id:4119888493 --> @urmel1960 commented on GitHub (Mar 24, 2026): How can I deploy an unstable buidl with my docker installation ?
GiteaMirror commented 2026-04-20 17:16:06 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Mar 24, 2026):

Check the docs: https://vikunja.io/docs/versions/#switching-between-versions

<!-- gh-comment-id:4120419384 --> @kolaente commented on GitHub (Mar 24, 2026): Check the docs: https://vikunja.io/docs/versions/#switching-between-versions
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
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/vikunja#6679
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?