Introduce separate entity object types for entity privileges
When granting or revoking a privilege on an entire entity, id 0 was used to indicate the fact that we don't grant a privilege on a single object, but on a whole entity. This caused confusion, because for entity USER, for example, id 0 is a valid object id (user 'guest' uses it). Any non-zero id dedicated to this cause obviously may be confused as well. Fix this by creating separate schema_object_types for entities: SC_ENTITY_SPACE, SC_ENTITY_SEQUENCE, etc. Closes #3574 Needed for #3524
Showing
- src/box/alter.cc 44 additions, 13 deletionssrc/box/alter.cc
- src/box/bootstrap.snap 0 additions, 0 deletionssrc/box/bootstrap.snap
- src/box/lua/schema.lua 35 additions, 23 deletionssrc/box/lua/schema.lua
- src/box/lua/upgrade.lua 23 additions, 0 deletionssrc/box/lua/upgrade.lua
- src/box/schema.cc 3 additions, 6 deletionssrc/box/schema.cc
- src/box/schema.h 13 additions, 10 deletionssrc/box/schema.h
- src/box/schema_def.c 17 additions, 0 deletionssrc/box/schema_def.c
- src/box/schema_def.h 15 additions, 1 deletionsrc/box/schema_def.h
- src/box/user.cc 15 additions, 12 deletionssrc/box/user.cc
- test/box-py/bootstrap.result 7 additions, 7 deletionstest/box-py/bootstrap.result
- test/box/access.result 3 additions, 3 deletionstest/box/access.result
- test/box/access_misc.result 4 additions, 4 deletionstest/box/access_misc.result
- test/box/alter.result 4 additions, 4 deletionstest/box/alter.result
- test/xlog/upgrade.result 7 additions, 7 deletionstest/xlog/upgrade.result
Loading
Please register or sign in to comment