You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Storage provider should work with all system tables and do hide implementation from all other modules. So generating Id should be part of storage provider because it can't access database at table-level. All other modules can access database schema level (can see only categories) and can't access tables.
Table Name
CRUD
Description
Context
Action
CRUD
Action to be applied to categories
System-wide replicated
Catalog
CRUD
Hierarchy to group entities
System-wide replicated
Category
CRU-
Category extracted from schemas
System-wide replicated
Config
CRUD
Globalstorage configuration
System-wide replicated
File
CRUD
File storage records
Server local table
Identifier
CRU-
Id index and pre-generated Ids
Global sharding
Log
CR--
Globalstorage access log
Server local table
Permission
CRUD
Permissions given to certain role
System-wide replicated
Role
CRUD
Roles (named groups of permissions)
System-wide replicated
Schema
CR--
Database schemas history
System-wide replicated
Session
CRUD
User sessions on this server
Server local table
Subdivision
CRU-
Organizational hierarchy
System-wide replicated
User
CRU-
User accounts and auth data
Global sharding
The text was updated successfully, but these errors were encountered:
Storage provider should work with all system tables and do hide implementation from all other modules. So generating Id should be part of storage provider because it can't access database at table-level. All other modules can access database schema level (can see only categories) and can't access tables.
CRUD
CRUD
CRU-
CRUD
CRUD
CRU-
CR--
CRUD
CRUD
CR--
CRUD
CRU-
CRU-
The text was updated successfully, but these errors were encountered: