Module physical_expr

Traits§

DynEq: PhysicalExpr can’t be constrained by Eq directly because it must remain object safe. To ease implementation, blanket implementation is provided for Eq types.
DynHash: PhysicalExpr can’t be constrained by Hash directly because it must remain object safe. To ease implementation blanket implementation is provided for Hash types.
PhysicalExpr: PhysicalExprs represent expressions such as A + 1 or CAST(c1 AS int).

down_cast_any_refDeprecated
fmt_sql: Prints a PhysicalExpr in a SQL-like format
format_physical_expr_list: Returns Display able a list of PhysicalExpr
is_dynamic_physical_expr: Check if the given PhysicalExpr is dynamic. Internally this calls snapshot_generation to check if the generation is non-zero, any dynamic PhysicalExpr should have a non-zero generation.
snapshot_generation: Check the generation of this PhysicalExpr. Dynamic PhysicalExprs may have a generation that is incremented every time the state of the PhysicalExpr changes. If the generation changes that means this PhysicalExpr or one of its children has changed since the last time it was evaluated.
snapshot_physical_expr: Take a snapshot of the given PhysicalExpr if it is dynamic.
with_new_children_if_necessary: Returns a copy of this expr if we change any child according to the pointer comparison. The size of children must be equal to the size of PhysicalExpr::children().