sql: new _trigger space format with space_id
As we would like to lookup triggers by space_id in future on space deletion to delete associated _trigger tuples we need to introduce new field space_id as secondary key. Part of #3273.
Showing
- src/box/bootstrap.snap 0 additions, 0 deletionssrc/box/bootstrap.snap
- src/box/lua/upgrade.lua 4 additions, 0 deletionssrc/box/lua/upgrade.lua
- src/box/schema_def.h 7 additions, 0 deletionssrc/box/schema_def.h
- src/box/sql.c 13 additions, 8 deletionssrc/box/sql.c
- src/box/sql/sqliteInt.h 2 additions, 0 deletionssrc/box/sql/sqliteInt.h
- src/box/sql/trigger.c 5 additions, 3 deletionssrc/box/sql/trigger.c
- test/app-tap/tarantoolctl.test.lua 1 addition, 1 deletiontest/app-tap/tarantoolctl.test.lua
- test/box-py/bootstrap.result 3 additions, 2 deletionstest/box-py/bootstrap.result
- test/box/access_misc.result 2 additions, 2 deletionstest/box/access_misc.result
- test/box/access_sysview.result 2 additions, 2 deletionstest/box/access_sysview.result
- test/box/alter.result 1 addition, 0 deletionstest/box/alter.result
- test/sql/gh2141-delete-trigger-drop-table.result 2 additions, 2 deletionstest/sql/gh2141-delete-trigger-drop-table.result
- test/sql/gh2141-delete-trigger-drop-table.test.lua 2 additions, 2 deletionstest/sql/gh2141-delete-trigger-drop-table.test.lua
- test/sql/persistency.result 4 additions, 4 deletionstest/sql/persistency.result
- test/sql/persistency.test.lua 4 additions, 4 deletionstest/sql/persistency.test.lua
- test/sql/upgrade.result 36 additions, 5 deletionstest/sql/upgrade.result
- test/sql/upgrade.test.lua 9 additions, 1 deletiontest/sql/upgrade.test.lua
Loading
Please register or sign in to comment