Struct Executed 

pub struct Executed {
    pub rows: Vec<Value>,
    pub project: Vec<Col>,
    pub has_rows: bool,
    pub tag: String,
    pub tag_counts_rows: bool,
}

One executed statement, held apart from any wire encoding.

This type is why the simple and extended protocols share an execution path rather than growing two copies of the SQL→NEDB semantics. The simple path encodes it immediately; the extended path parks it in a portal and dribbles the rows out across successive Execute messages. Both get identical answers because both call execute_stmt.

Fields

rows: Vec<Value>

The rows the client gets — a SELECT’s result, or a write’s RETURNING.

project: Vec<Col>

How to project them (empty = every key in the row).

has_rows: bool

Whether the client asked for rows at all. Distinct from rows.is_empty(): a SELECT matching nothing still owes a RowDescription, while an UPDATE without RETURNING owes NoData.

tag: String

The command tag, already rendered — except for a SELECT, where the row count is only known once the rows have actually been sent.

tag_counts_rows: bool

True when tag is a SELECT-shaped tag whose count is the rows sent.