Method values

datafusion/expr/src/logical_plan/builder.rs:210–231

Create a values list based relation, and the schema is inferred from data, consuming `value`. See the [Postgres VALUES](https://www.postgresql.org/docs/current/queries-values.html) documentation for more details. so it's usually better to override the default names with a table alias list. If the values include params/binders such as $1, $2, $3, etc, then the `param_data_types` should be provide

(values: Vec<Vec<Expr>>)

    ///
    /// If the values include params/binders such as $1, $2, $3, etc, then the `param_data_types` should be provided.
    pub fn values(values: Vec<Vec<Expr>>) -> Result<Self> {
        if values.is_empty() {
            return plan_err!("Values list cannot be empty");
        }
        let n_cols = values[0].len();
        if n_cols == 0 {
            return plan_err!("Values list cannot be zero length");
        }
        for (i, row) in values.iter().enumerate() {
            if row.len() != n_cols {
                return plan_err!(
                    "Inconsistent data length across values list: got {} values in row {} but expected {}",
                    row.len(),
                    i,
                    n_cols
                );
            }
        }

        // Infer from data itself
        Self::infer_data(values)
    }

    /// Create a values list based relation, and the schema is inferred from data itself or table schema if provided, consuming
    /// `value`. See the [Postgres VALUES](https://www.postgresql.org/docs/current/queries-values.html)