3 ms·
How about having sql statements default to “dry run”, only executing if an additional keyword (like “execute”) is added.
by bazoom42 3y ago
How about having sql statements default to “dry run”, only executing if an additional keyword (like “execute”) is added.
- byteknight 3y agoThat becomes a non-boundary because you'd write it every time.
- pak9rabid 3y agoIsn't this something that explicit transactions (BEGIN/COMMIT/ROLLBACK) do? Many DB clients can be configured to have autocommit disabled, so that you're forced to either COMMIT or ROLLBACK each transaction.