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

[PR #2455] [MERGED] fix: use MySQL-compatible CREATE INDEX in migration 20260224215050 #9999

New Issue
Closed
opened 2026-04-23 09:20:08 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-23 09:20:08 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/go-vikunja/vikunja/pull/2455
Author: @tink-bot
Created: 3/23/2026
Status: ✅ Merged
Merged: 3/23/2026
Merged by: @kolaente

Base: main ← Head: fix/mysql-create-index-migration-2431

📝 Commits (1)

  • deab991 fix: use MySQL-compatible CREATE INDEX in migration 20260224215050

📊 Changes

1 file changed (+16 additions, -2 deletions)

View changed files

📝 pkg/migration/20260224215050.go (+16 -2)

📄 Description

Migration 20260224215050 uses CREATE INDEX IF NOT EXISTS, which is not valid MySQL syntax, causing a SQL error (1064) and crash loop for all MySQL users upgrading to 2.2.0.

This switches on the database type to use IF NOT EXISTS only for Postgres/SQLite, and plain CREATE INDEX with duplicate key error suppression (Error 1061) for MySQL — matching the pattern already used in migrations 20241028131622 and 20251108154913.

Fixes #2431

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/go-vikunja/vikunja/pull/2455 **Author:** [@tink-bot](https://github.com/tink-bot) **Created:** 3/23/2026 **Status:** ✅ Merged **Merged:** 3/23/2026 **Merged by:** [@kolaente](https://github.com/kolaente) **Base:** `main` ← **Head:** `fix/mysql-create-index-migration-2431` --- ### 📝 Commits (1) - [`deab991`](https://github.com/go-vikunja/vikunja/commit/deab991d2d1061ebd002e3519a3a938654c7ced5) fix: use MySQL-compatible CREATE INDEX in migration 20260224215050 ### 📊 Changes **1 file changed** (+16 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `pkg/migration/20260224215050.go` (+16 -2) </details> ### 📄 Description Migration 20260224215050 uses `CREATE INDEX IF NOT EXISTS`, which is not valid MySQL syntax, causing a SQL error (1064) and crash loop for all MySQL users upgrading to 2.2.0. This switches on the database type to use `IF NOT EXISTS` only for Postgres/SQLite, and plain `CREATE INDEX` with duplicate key error suppression (Error 1061) for MySQL — matching the pattern already used in migrations 20241028131622 and 20251108154913. Fixes #2431 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-23 09:20:08 -05:00
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 pull-request
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#9999
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?