upsert: review fixes
- upsert semantics is update or insert, not "always update" - upsert doesn't return tuple - bind upsert as tuple method in Lua (useful for QA) - ensure upsert is properly encoded in xlog
Showing
- src/box/iproto_constants.c 7 additions, 4 deletionssrc/box/iproto_constants.c
- src/box/iproto_constants.h 4 additions, 7 deletionssrc/box/iproto_constants.h
- src/box/lua/call.cc 9 additions, 9 deletionssrc/box/lua/call.cc
- src/box/lua/tuple.cc 14 additions, 0 deletionssrc/box/lua/tuple.cc
- src/box/lua/tuple.lua 19 additions, 1 deletionsrc/box/lua/tuple.lua
- src/box/request.cc 43 additions, 40 deletionssrc/box/request.cc
- src/box/request.h 5 additions, 5 deletionssrc/box/request.h
- src/box/tuple.cc 22 additions, 33 deletionssrc/box/tuple.cc
- src/box/tuple.h 1 addition, 19 deletionssrc/box/tuple.h
- src/box/tuple_update.cc 2 additions, 3 deletionssrc/box/tuple_update.cc
- src/box/tuple_update.h 1 addition, 1 deletionsrc/box/tuple_update.h
- test/big/lua.result 1 addition, 1 deletiontest/big/lua.result
- test/box/tuple.result 13 additions, 13 deletionstest/box/tuple.result
- test/box/update.result 64 additions, 17 deletionstest/box/update.result
- test/box/update.test.lua 15 additions, 0 deletionstest/box/update.test.lua
- test/replication/init_storage.result 3 additions, 0 deletionstest/replication/init_storage.result
- test/replication/init_storage.test.py 1 addition, 0 deletionstest/replication/init_storage.test.py
Loading
Please register or sign in to comment