MokoConsulting/MokoGitea-APP
1
0
Fork 0
Code Issues 157 Pull Requests 3 Releases 96 Wiki Activity

tech-debt: Migration framework does not handle foreign keys #329

New Issue
Open
opened 2026-05-31 14:23:34 +00:00 by jmiller · 0 comments
jmiller commented 2026-05-31 14:23:34 +00:00
Owner
Copy Link
Copy Source

Summary

Database migration code cannot handle tables with foreign keys.

Locations

  • models/migrations/base/db.go:45 - will not work if there are foreign keys
  • models/migrations/base/db.go:311 - will not work if there are foreign keys
  • models/db/driver_sqlite_modernc.go:30 - changed behavior from mattn driver

Action Required

Add foreign key handling to migration framework. Document SQLite driver behavior differences.

Created by Claude Opus 4.6

## Summary Database migration code cannot handle tables with foreign keys. ## Locations - `models/migrations/base/db.go:45` - will not work if there are foreign keys - `models/migrations/base/db.go:311` - will not work if there are foreign keys - `models/db/driver_sqlite_modernc.go:30` - changed behavior from mattn driver ## Action Required Add foreign key handling to migration framework. Document SQLite driver behavior differences. --- *Created by Claude Opus 4.6*
jmiller added the tech-debtupstream labels 2026-05-31 14:23:34 +00:00
Sign in to join this conversation.
Labels
Clear labels
breaking-change
Breaking API or behavior change
 ci-cd
CI/CD pipeline changes
 config
Configuration changes
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 docker
Docker/container changes
 documentation
Documentation changes
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 mokostandards
Related to MokoStandards framework
 push-failure
Git push operation failed
 security
Security vulnerability or hardening
 size/l
200-500 lines changed
 size/m
50-200 lines changed
 size/s
10-50 lines changed
 size/xl
500+ lines changed
 size/xs
< 10 lines changed
 standards-drift
Deviates from MokoStandards
 standards-update
MokoStandards compliance update
 sync-failure
Sync or mirror failed
 tech-debt
Technical debt and TODO/FIXME items
 upstream
upstream
Inherited from upstream Gitea
 work-in-progress
Draft or incomplete work
No labels tech-debt upstream
Priority Low
Type Task
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller) moko-deploy (Moko Deploy Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGitea-APP#329
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?