tuple: drop extra restrictions for multikey index
Multikey index did not work properly with nullable root field in tuple_raw_multikey_count(). Now it is fixed and corresponding restrictions are dropped. This also means that we can drop implicit nullability update for array/map fields and make all fields nullable by default, as it was until e1d3fe8a (tuple format: don't allow null where array/map is expected), as far as default non-nullability itself doesn't solve any real problems while providing confusing behavior (gh-5027). Follow-up #5027 Closes #5192
Showing
- src/box/memtx_space.c 0 additions, 8 deletionssrc/box/memtx_space.c
- src/box/tuple.c 4 additions, 1 deletionsrc/box/tuple.c
- src/box/tuple_format.c 0 additions, 20 deletionssrc/box/tuple_format.c
- src/box/vinyl.c 0 additions, 8 deletionssrc/box/vinyl.c
- test/engine/gh-5027-fields-nullability.result 5 additions, 58 deletionstest/engine/gh-5027-fields-nullability.result
- test/engine/gh-5027-fields-nullability.test.lua 5 additions, 22 deletionstest/engine/gh-5027-fields-nullability.test.lua
- test/engine/gh-5192-multikey-root-nullability.result 59 additions, 0 deletionstest/engine/gh-5192-multikey-root-nullability.result
- test/engine/gh-5192-multikey-root-nullability.test.lua 19 additions, 0 deletionstest/engine/gh-5192-multikey-root-nullability.test.lua
- test/engine/json.result 10 additions, 10 deletionstest/engine/json.result
- test/engine/json.test.lua 3 additions, 3 deletionstest/engine/json.test.lua
- test/engine/multikey.result 4 additions, 4 deletionstest/engine/multikey.result
- test/engine/multikey.test.lua 2 additions, 2 deletionstest/engine/multikey.test.lua
Loading
Please register or sign in to comment