feat: enhance drop statement warnings with user confirmation #3918
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
--confirm-drops
option to control drop warning behaviorMotivation
Currently,
supabase db diff
shows a weak warning when DROP statements are detected. This is particularly problematic for column renames, which are detected as DROP COLUMN + ADD COLUMN operations, potentially causing data loss.Changes
--confirm-drops
option with three modes:prompt
(default): Show interactive confirmation promptskip
: Bypass confirmation and proceed automaticallydeny
: Always refuse operations with DROP statementsTest plan
showDropWarningAndConfirm
function--confirm-drops
option handling--confirm-drops
modesExample output
New option usage
🤖 Generated with Claude Code