pub struct Run<'a> {
pub conn: &'a mut Conn,
pub policy: &'a Policy,
pub write_state: &'a mut WriteState,
pub server_read_only: bool,
pub conversion: &'a Conversion,
pub stop_on_failure: bool,
}Expand description
Everything running one statement of a file takes.
The five describe one thing, which is how a statement is to be run: on which connection, under which policy, against which record of what has already been written, on a destination that may refuse change of its own, and with which reading of the server’s types. Carried apart, every function that runs a statement had to repeat the same list, and every new one had to repeat it again in the same order.
Fields§
§conn: &'a mut ConnThe connection every statement is asked on.
policy: &'a PolicyWhat this invocation admits.
write_state: &'a mut WriteStateWhat has already been written, and what that now demands.
server_read_only: boolWhether the destination itself refuses change.
conversion: &'a ConversionHow the server’s own types are read back.
stop_on_failure: boolWhether a statement that failed ends the run.
True everywhere but a file whose caller asked to carry on. A block is never allowed to carry on, because a block that skipped a statement and was then confirmed is precisely the half-applied script FR-029 forbids.