Safe mode and review in SQL Server

Review SQL Server writes before execution and reject stale rowversion values.

Tablyne reviews SQL Server writes before they reach the server and does not overwrite a row changed by another session.

Review-first sequence

  1. Identify the SQL Server connection and target relation.
  2. Stage the changed fields.
  3. Show the generated SQL and its identity predicate.
  4. Read the current rowversion.
  5. Apply the write only if the version still matches.
  6. Roll back the batch when the check fails.

The version check is part of the write condition, not an after-the-fact warning. A stale rowversion must produce a conflict result. The user can then reload the row and decide whether to stage the change again.

Query safety

A query-console statement needs the same review boundary when it writes data. Tablyne separates read-only work from INSERT, UPDATE, DELETE and DDL, and makes the selected safety policy visible before execution.

Use Ctrl+S for pending grid changes and Ctrl+Enter for the current SQL statement.

The review keeps the rowversion check visible from the staged edit through the commit decision.