box: always set index.parts.exclude_null to true or false
Currently the `exclude_null` field of `index_object.parts` is inconsistent between local box and net.box connection. It returns the following values: - locally: true / null - net.box: true / false This mismatch makes it difficult to compare schemas on the storage and via the net.box connection on the router (see tarantool/crud#361). Closes #8649 NO_DOC=minor
Showing
- changelogs/unreleased/gh-8649-always-set-exclude_null-to-true-or-false.md 4 additions, 0 deletions...eased/gh-8649-always-set-exclude_null-to-true-or-false.md
- src/box/lua/key_def.c 2 additions, 4 deletionssrc/box/lua/key_def.c
- test/box-luatest/gh_7356_index_parts_methods_test.lua 6 additions, 3 deletionstest/box-luatest/gh_7356_index_parts_methods_test.lua
- test/box-tap/key_def.test.lua 12 additions, 5 deletionstest/box-tap/key_def.test.lua
- test/box/alter.result 4 additions, 0 deletionstest/box/alter.result
- test/box/errinj.result 2 additions, 0 deletionstest/box/errinj.result
- test/box/gh-5998-one-tx-for-ddl.result 1 addition, 0 deletionstest/box/gh-5998-one-tx-for-ddl.result
- test/box/lua.result 2 additions, 0 deletionstest/box/lua.result
- test/box/misc.result 16 additions, 9 deletionstest/box/misc.result
- test/box/rtree_misc.result 1 addition, 0 deletionstest/box/rtree_misc.result
- test/box/tx_man.result 1 addition, 0 deletionstest/box/tx_man.result
- test/engine/ddl.result 17 additions, 0 deletionstest/engine/ddl.result
- test/engine/null.result 27 additions, 12 deletionstest/engine/null.result
- test/sql/types.result 8 additions, 0 deletionstest/sql/types.result
- test/vinyl/ddl.result 1 addition, 0 deletionstest/vinyl/ddl.result
Loading
Please register or sign in to comment