For statements with no result set (INSERT/UPDATE/DELETE/MERGE/DDL), prints a single indented line with a green checkmark, the engine's message, and the elapsed time in milliseconds.
## Overview Statements that do not produce a result set (DML, DDL, pipeline control statements) do not flow through the tabular renderer. Instead the CLI prints a single status line per statement, summarising what the engine reported and how long the request took. ## Behavior - The line is produced by `print_dml_result(message, elapsed_ms)` and has the shape ` ✔ <message> (<elapsed>ms)`. The leading two spaces match the indent used by `compact` output so DML and tabular output align when mixed in one log. - The checkmark glyph (U+2714) is rendered green. The message text itself is also rendered green. The `(<elapsed>ms)` suffix is part of the same `println!` but is not styled. - `<message>` is whatever text the engine returned for the statement. When the engine returns no message, the CLI substitutes `OK`. Common messages include `OK`, `Table created`, `Inserted <n> rows`, and so on; exact wording is engine-defined and may evolve. - The line is written to stdout. Errors are never reported through this renderer; they go to stderr via `print_error`. - The `--format` flag is ignored for DML results. `table`, `compact`, and `json` all produce the same single-line output, because there is no tabular payload to serialise.
INSERT INTO orders ... -> ' ✔ OK (123ms)'CREATE TABLE ... -> ' ✔ Table created (45ms)'