kodev-org
/
vikunja
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix(kanban): qualify task_buckets table with configured schema in upsert 

The native upsert uses raw SQL, which bypasses xorm's bean-based table-name
handling and would target the default schema instead of a configured
postgres database.schema. Resolve the schema-qualified table name via the
engine so bucket moves keep working on schema-configured deployments.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JK7JwuvjhcsNf5d5fUopeY
This commit is contained in:
Claude 2026-06-18 22:14:44 +00:00
parent de674b5a2c
commit a76cfd036c
No known key found for this signature in database
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
pkg/models/kanban_task_bucket.go
View File

@ -68,7 +68,10 @@ func (b *TaskBucket) upsert(s *xorm.Session) (err error) {
onConflict = "ON DUPLICATE KEY UPDATE bucket_id = VALUES(bucket_id)"
}
query := "INSERT INTO task_buckets (task_id, project_view_id, bucket_id) VALUES (?, ?, ?) " + onConflict
// Raw SQL bypasses xorm's bean-based table-name handling, so qualify the
// table ourselves to honor a configured postgres schema (database.schema).
table := s.Engine().TableName(b, true)
query := "INSERT INTO " + table + " (task_id, project_view_id, bucket_id) VALUES (?, ?, ?) " + onConflict
_, err = s.Exec(query, b.TaskID, b.ProjectViewID, b.BucketID)
return
}