fix: name normalization
The name normalization in Tarantool can be a little bit confusing because it has two different pipelines: for SQL and for YAML configuration. 1. SQL allows us to use table and column names with a rule: the name in the double quotes is processed "as is" while a name without double quotes is transformed to the upper case. Here are the examples: select * from t .. -> "T" select * from T .. -> "T" select * from "T" .. -> "T" select * from "t" .. -> "t" So, the only way to get in Tarantool a name with lowercase characters is to wrap it with double quotes. 2. YAML configuration allows us to create distributed tables with the following naming convention: the name is always processed "as is". For example: t -> "t" T -> "T"
Showing
- benches/engine.rs 3 additions, 3 deletionsbenches/engine.rs
- src/executor/engine.rs 16 additions, 16 deletionssrc/executor/engine.rs
- src/executor/engine/cartridge/backend/sql/ir/tests.rs 3 additions, 3 deletionssrc/executor/engine/cartridge/backend/sql/ir/tests.rs
- src/executor/engine/cartridge/config.rs 33 additions, 5 deletionssrc/executor/engine/cartridge/config.rs
- src/executor/engine/cartridge/config/tests.rs 2 additions, 2 deletionssrc/executor/engine/cartridge/config/tests.rs
- src/executor/engine/cartridge/router.rs 3 additions, 2 deletionssrc/executor/engine/cartridge/router.rs
- src/executor/engine/mock.rs 6 additions, 5 deletionssrc/executor/engine/mock.rs
- src/executor/tests.rs 13 additions, 13 deletionssrc/executor/tests.rs
- src/frontend/sql.rs 40 additions, 29 deletionssrc/frontend/sql.rs
- src/frontend/sql/ir.rs 0 additions, 7 deletionssrc/frontend/sql/ir.rs
- src/frontend/sql/ir/tests.rs 5 additions, 5 deletionssrc/frontend/sql/ir/tests.rs
- src/ir/operator.rs 4 additions, 1 deletionsrc/ir/operator.rs
- test_app/test/integration/api_test.lua 48 additions, 0 deletionstest_app/test/integration/api_test.lua
Loading
Please register or sign in to comment