fix: subtree iterator traversal order
Previously we had an error in the parameter binding order when a query had sub-queries in filters or join conditions.
Showing
- src/executor/engine/cartridge/backend/sql/ir.rs 1 addition, 1 deletionsrc/executor/engine/cartridge/backend/sql/ir.rs
- src/executor/engine/cartridge/backend/sql/tree.rs 1 addition, 1 deletionsrc/executor/engine/cartridge/backend/sql/tree.rs
- src/executor/shard.rs 1 addition, 1 deletionsrc/executor/shard.rs
- src/frontend/sql.rs 1 addition, 1 deletionsrc/frontend/sql.rs
- src/frontend/sql/ir/tests.rs 3 additions, 71 deletionssrc/frontend/sql/ir/tests.rs
- src/frontend/sql/ir/tests/params.rs 128 additions, 0 deletionssrc/frontend/sql/ir/tests/params.rs
- src/ir/explain.rs 2 additions, 2 deletionssrc/ir/explain.rs
- src/ir/expression.rs 23 additions, 9 deletionssrc/ir/expression.rs
- src/ir/operator.rs 1 addition, 1 deletionsrc/ir/operator.rs
- src/ir/tree.rs 55 additions, 12 deletionssrc/ir/tree.rs
Loading
Please register or sign in to comment