sql: use vtab::rowid_next() instead of index_max()
After introducing separate method in space's vtab to fetch next rowid value, lets use it in SQL internals. This allows us to fix incorrect results of queries involving storing equal tuples in ephemeral spaces. Closes #3297
Showing
- src/box/errcode.h 1 addition, 0 deletionssrc/box/errcode.h
- src/box/sql.c 1 addition, 27 deletionssrc/box/sql.c
- src/box/sql/insert.c 3 additions, 14 deletionssrc/box/sql/insert.c
- src/box/sql/select.c 6 additions, 6 deletionssrc/box/sql/select.c
- src/box/sql/tarantoolInt.h 0 additions, 13 deletionssrc/box/sql/tarantoolInt.h
- src/box/sql/vdbe.c 25 additions, 14 deletionssrc/box/sql/vdbe.c
- test/box/misc.result 1 addition, 0 deletionstest/box/misc.result
- test/sql-tap/gh-3297-ephemeral-rowid.test.lua 30 additions, 0 deletionstest/sql-tap/gh-3297-ephemeral-rowid.test.lua
Loading
Please register or sign in to comment