sql: set explicit default collation's strength
Before the patch, collations with no strength set used tertiary strength. But it was not easy to understand it, because box.space._collation:select{} would return ... [1, 'unicode', 1, 'ICU', '', {}] ... for such collations. After the patch default value is set explicitly, so user would observe : ... [1, 'unicode', 1, 'ICU', '', {strength='tertiary'}] ... Closes #3573 @TarantoolBot document Title: default collation strength is explicit tertiary now Before the patch we already have tertiary strength is default strength for collations, but it was implicit: [1, 'unicode', 1, 'ICU', '', {}] After the patch it's just become explicit: 1, 'unicode', 1, 'ICU', '', {'strength' = 'tertiary'}] Also please fix this https://tarantool.io/en/doc/2.1/book/box/data_model/#collations There is line saying: "unicode collation observes all weights, from L1 to Ln (identical)" It was not true and now this fact would just become obvious.
Showing
- src/box/bootstrap.snap 0 additions, 0 deletionssrc/box/bootstrap.snap
- src/box/lua/schema.lua 4 additions, 0 deletionssrc/box/lua/schema.lua
- src/box/lua/upgrade.lua 22 additions, 1 deletionsrc/box/lua/upgrade.lua
- src/lua/utf8.c 1 addition, 0 deletionssrc/lua/utf8.c
- test/box-py/bootstrap.result 1 addition, 1 deletiontest/box-py/bootstrap.result
- test/box/ddl.result 3 additions, 3 deletionstest/box/ddl.result
- test/sql/collation.result 11 additions, 0 deletionstest/sql/collation.result
- test/sql/collation.test.lua 7 additions, 0 deletionstest/sql/collation.test.lua
- test/unit/coll.cpp 2 additions, 0 deletionstest/unit/coll.cpp
Loading
Please register or sign in to comment