fix(desktop): resolve migration idempotency for 11 by making it noop and using a new col#826
Conversation
…istence column The migration 0011 failed on app start for users who already had the terminal_persistence column. This fix: - Makes migration 0011 a no-op (SELECT 1) to avoid duplicate column error - Adds migration 0012 with new column name `persist_terminal` - Renames schema field from `terminalPersistence` to `persistTerminal` - Changes default value from false to true
📝 WalkthroughWalkthroughThe changes rename the terminal persistence database column from Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🧹 Preview Cleanup CompleteThe following preview resources have been cleaned up:
Thank you for your contribution! 🎉 |
Summary
SELECT 1) to avoid duplicate column error for users who already hadterminal_persistencepersist_terminal(withDEFAULT true)terminalPersistencetopersistTerminalfalsetotrueTest plan
terminal_persistencecolumn: migration 0011 skips, 0012 adds new columntruefor new installationsSummary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.