Function validate_procedure_statement

graphlite/src/ast/validator.rs:2570–2596

Validate a statement within a procedure body context In procedure bodies, statements have different validation rules: - MATCH statements don't require RETURN clauses when followed by NEXT - Data statements (like DELETE) don't require RETURN clauses

(
    statement: &Statement,
    ctx: &ValidationContext,
    errors: &mut Vec<ValidationError>,
)

/// - MATCH statements don't require RETURN clauses when followed by NEXT
/// - Data statements (like DELETE) don't require RETURN clauses
fn validate_procedure_statement(
    statement: &Statement,
    ctx: &ValidationContext,
    errors: &mut Vec<ValidationError>,
) {
    match statement {
        Statement::Query(query) => {
            // For query statements in procedure bodies, validate without requiring RETURN clause
            validate_procedure_query(query, ctx, errors);
        }
        Statement::DataStatement(_data_stmt) => {
            // Data statements (like DELETE) in procedure bodies don't require RETURN clauses
            // Just validate that the statement structure is valid, but don't require RETURN
            // TODO: Implement basic data statement validation without RETURN requirement
        }
        _ => {
            // For other statement types, use general validation
            let doc = Document {
                statement: statement.clone(),
                location: Default::default(),
            };
            if let Err(mut nested_errors) = validate_query(&doc, ctx.has_graph_context) {
                errors.append(&mut nested_errors);
            }
        }
    }
}

/// Validate catalog statement (DDL operations)
fn validate_catalog_statement(