Safe mode and review in MySQL
Review MySQL SQL, choose safe mode and compare the current row token before an UPDATE or DELETE.
The connection form exposes read-only and safe mode. Safe mode has the same three labels used by the connection metadata: dangerous (default), confirm writes and confirm all.
Select the guard
- Use dangerous (default) only when the connection is intentionally permissive.
- Use confirm writes to confirm INSERT, UPDATE, DELETE and DDL.
- Use confirm all when SELECT should also stop for a confirmation.
The read-only setting is a session mark, not an absolute server privilege. The app’s own text explains the boundary: it catches a slip of the finger, but it is not a hard guarantee because a statement can change the mark or open an explicitly writable transaction. A MySQL user without write permission is the hard database-level control.
Review a grid write
A staged grid update is rendered as an UPDATE with the changed columns and identity predicate. If the row has a token, Tablyne runs a transaction and re-reads the row using SELECT ... FOR UPDATE. It compares the full current row with the token captured when the page was read. Only after that comparison succeeds does it run the write.
The rendered review text includes the re-read and explains that the comparison happens in memory. Running that SQL by hand does not recreate the protection: the manual script would lock the row but would not compare the token before the following UPDATE or DELETE.
Use Ctrl+S to commit pending grid changes, Ctrl+Z to undo and Ctrl+Y to redo. If a conflict is reported, reload the row and stage the intended value again.