Skip confirmation prompts for dangerous SQL (DROP, DELETE without WHERE, UPDATE without WHERE, TRUNCATE).
--force | -y## Overview `--force` (aliased as `-y`) is documented to bypass the interactive confirmation prompt that fires for dangerous SQL statements such as `DROP TABLE`, unqualified `DELETE`, unqualified `UPDATE`, and `TRUNCATE`. In the current build, the dangerous-SQL confirmation path is implemented only inside the `--classic` REPL. Non-classic surfaces (the interactive shell, `query`, `run`, piped stdin) do not prompt for confirmation, so the flag has nothing to suppress on those surfaces. ## Behavior - Inside the `--classic` REPL, the flag suppresses the confirmation prompt and the destructive statement is sent straight to the engine. - Outside `--classic`, the flag is parsed and accepted but has no confirmation prompt to bypass. The statement runs either way. - Applies for the lifetime of the process. Enabling it once affects every statement issued in the classic REPL during that session. - Intended for CI and unattended automation that already knows the script is destructive. ## Compatibility - The classic REPL is opted into with `--classic`. Without that flag, DeltaForge launches the interactive shell, which has no dangerous-SQL confirmation, and `--force` is effectively a no-op. - `query`, `run`, and piped stdin execute statements directly without a confirmation step; they run destructive SQL without prompting regardless of `--force`.
# Suppress confirmation inside the --classic REPL for an automation session
delta-forge-cli --classic --force# Short form, same effect
delta-forge-cli --classic -y# In non-classic surfaces the flag is accepted but has no confirmation to bypass
delta-forge-cli --force run scripts/cleanup.sql# Single-statement destructive query; --force is a no-op here because query has no prompt
delta-forge-cli -y query 'DROP TABLE staging.tmp_events'