github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-07-15 22:32:29 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #2589] [MySQL 8.0] Tasks not showing after upgrade to Vikunja 2.3.0 #6703

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

Originally created by @chandrashekharkavi-tech on GitHub (Apr 10, 2026).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2589

Pre-submission checklist

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

Description

After upgrading from Vikunja 2.2.2 → 2.3.0 using Docker Compose, tasks no longer appear in the web UI. The backend logs show SQL syntax errors when fetching tasks.

Error Trace (from logs):
time=2026-04-10T05:15:09.879Z level=ERROR component=http remote_ip=172.18.0.1 method=GET uri="/api/v1/tasks?..." status=500 latency=6.411034ms err="Error 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'int)) AS is_archived, all_projects.background_file_id, all_projects.background_b' at line 5"

Steps to Reproduce:

Upgrade Vikunja from 2.2.2 to 2.3.0 in Docker Compose.

Access tasks via web UI.

Observe missing tasks.

Expected Behavior:
Tasks should display normally after upgrade.

Actual Behavior:
Tasks fail to load due to SQL syntax error in MySQL 8.0.

Vikunja Version

2.3.0

Browser and version

Microsoft Edge is up to date. Version 146.0.3856.109 (Official build) (64-bit)

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @chandrashekharkavi-tech on GitHub (Apr 10, 2026). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2589 ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same problem. ### Description After upgrading from Vikunja 2.2.2 → 2.3.0 using Docker Compose, tasks no longer appear in the web UI. The backend logs show SQL syntax errors when fetching tasks. Error Trace (from logs): time=2026-04-10T05:15:09.879Z level=ERROR component=http remote_ip=172.18.0.1 method=GET uri="/api/v1/tasks?..." status=500 latency=6.411034ms err="Error 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'int)) AS is_archived, all_projects.background_file_id, all_projects.background_b' at line 5" Steps to Reproduce: Upgrade Vikunja from 2.2.2 to 2.3.0 in Docker Compose. Access tasks via web UI. Observe missing tasks. Expected Behavior: Tasks should display normally after upgrade. Actual Behavior: Tasks fail to load due to SQL syntax error in MySQL 8.0. ### Vikunja Version 2.3.0 ### Browser and version Microsoft Edge is up to date. Version 146.0.3856.109 (Official build) (64-bit) ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror added the area/databasedb/mysqlconcern/regression labels 2026-04-20 17:17:11 -05:00
GiteaMirror commented 2026-04-20 17:17:12 -05:00
Author
Owner
Copy Link

@sbraaa commented on GitHub (Apr 10, 2026):

Same configuration and same problem for me!

<!-- gh-comment-id:4222405359 --> @sbraaa commented on GitHub (Apr 10, 2026): Same configuration and same problem for me!
GiteaMirror commented 2026-04-20 17:17:12 -05:00
Author
Owner
Copy Link

@gabrielebellani commented on GitHub (Apr 10, 2026):

Same here. Every task and project GET requests return 500.
Here is the Docker logs:

vikunja-1  | time=2026-04-10T13:09:29.425Z level=ERROR component=http remote_ip=xxx.xxx.xxx.xxx method=GET uri="/api/v1/projects?is_archived=true&expand=permissions&page=1" status=500 latency=993.515µs err="Error 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'int)) AS is_archived, all_projects.background_file_id, all_projects.background_b' at line 5"
vikunja-1  | time=2026-04-10T13:09:29.425Z level=ERROR component=http remote_ip=xxx.xxx.xxx.xxx method=GET uri="/api/v1/labels?page=1" status=500 latency=5.390936ms err="Error 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'int)) AS is_archived, all_projects.background_file_id, all_projects.background_b' at line 5
<!-- gh-comment-id:4224053109 --> @gabrielebellani commented on GitHub (Apr 10, 2026): Same here. Every task and project GET requests return 500. Here is the Docker logs: ``` vikunja-1 | time=2026-04-10T13:09:29.425Z level=ERROR component=http remote_ip=xxx.xxx.xxx.xxx method=GET uri="/api/v1/projects?is_archived=true&expand=permissions&page=1" status=500 latency=993.515µs err="Error 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'int)) AS is_archived, all_projects.background_file_id, all_projects.background_b' at line 5" vikunja-1 | time=2026-04-10T13:09:29.425Z level=ERROR component=http remote_ip=xxx.xxx.xxx.xxx method=GET uri="/api/v1/labels?page=1" status=500 latency=5.390936ms err="Error 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'int)) AS is_archived, all_projects.background_file_id, all_projects.background_b' at line 5 ```
GiteaMirror commented 2026-04-20 17:17:13 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Apr 10, 2026):

Can you enable the databse and debug logs and share the output?

https://vikunja.io/docs/config-options/#1-log-database

Are you all using MySQL 8?

<!-- gh-comment-id:4227345528 --> @kolaente commented on GitHub (Apr 10, 2026): Can you enable the databse and debug logs and share the output? https://vikunja.io/docs/config-options/#1-log-database Are you all using MySQL 8?
GiteaMirror commented 2026-04-20 17:17:13 -05:00
Author
Owner
Copy Link

@vikunja-bot-app[bot] commented on GitHub (Apr 11, 2026):

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

<!-- gh-comment-id:4229860392 --> @vikunja-bot-app[bot] commented on GitHub (Apr 11, 2026): This issue has been fixed in [`5b2cbcb`](), 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:17:13 -05:00
Author
Owner
Copy Link

@Anduin2017 commented on GitHub (Apr 13, 2026):

Can we release 2.3.1 ASAP? All our customers are running latest stable and are having this issue.

<!-- gh-comment-id:4234516065 --> @Anduin2017 commented on GitHub (Apr 13, 2026): Can we release 2.3.1 ASAP? All our customers are running latest stable and are having this issue.
GiteaMirror commented 2026-04-20 17:17:14 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Apr 17, 2026):

@Anduin2017 happy to talk about commercial support for things like this, send me an email if you're interested

<!-- gh-comment-id:4267581707 --> @kolaente commented on GitHub (Apr 17, 2026): @Anduin2017 happy to talk about commercial support for things like this, send me an email if you're interested
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 area/database concern/regression db/mysql
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#6703
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?