the statement's shape with literals and bindings as ?; null when it carried no SQL
the first bound parameter when short (a cid on a cache bin); later ones are payload
the capability crossed for; cfwSqlExec and cfwSqlTxn are the only ones carrying SQL
bytes the host returned, so a cheap statement with an expensive reply is visible
rows handed back across the bridge, which is not rowsRead
rows SQLite touched, which is what the row-read meter charges
rows written
the table read or written
true when the statement arrived inside a cfwSqlTxn batch rather than on its own
one statement, decomposed far enough to classify it