refactoring: introduce ordered syntax nodes
The main goal of this refactoring is to get a syntax data node vector in the order for building SQL query in a more clear manner.
Showing
- benches/engine.rs 5 additions, 5 deletionsbenches/engine.rs
- benches/parse.rs 5 additions, 5 deletionsbenches/parse.rs
- src/executor/engine/cartridge/backend/sql/ir.rs 2 additions, 45 deletionssrc/executor/engine/cartridge/backend/sql/ir.rs
- src/executor/engine/cartridge/backend/sql/ir/tests.rs 37 additions, 29 deletionssrc/executor/engine/cartridge/backend/sql/ir/tests.rs
- src/executor/engine/cartridge/backend/sql/tree.rs 61 additions, 0 deletionssrc/executor/engine/cartridge/backend/sql/tree.rs
- src/executor/engine/cartridge/backend/sql/tree/tests.rs 4 additions, 4 deletionssrc/executor/engine/cartridge/backend/sql/tree/tests.rs
- src/executor/engine/cartridge/router.rs 7 additions, 6 deletionssrc/executor/engine/cartridge/router.rs
- src/executor/engine/mock.rs 6 additions, 6 deletionssrc/executor/engine/mock.rs
- src/ir/transformation/helpers.rs 6 additions, 5 deletionssrc/ir/transformation/helpers.rs
Loading
Please register or sign in to comment