Modules§
- annotation
- Nested message and enum types in
Annotation
. - authentication
- Nested message and enum types in
Authentication
. - concept
- Nested message and enum types in
Concept
. - concept_
document - Nested message and enum types in
ConceptDocument
. - connection
- Nested message and enum types in
Connection
. - database
- Nested message and enum types in
Database
. - database_
manager - Nested message and enum types in
DatabaseManager
. - database_
replicas - Nested message and enum types in
DatabaseReplicas
. - options
- Nested message and enum types in
Options
. - query
- Nested message and enum types in
Query
. - row_
entry - Nested message and enum types in
RowEntry
. - server_
manager - Nested message and enum types in
ServerManager
. - thing
- Nested message and enum types in
Thing
. - transaction
- Nested message and enum types in
Transaction
. - type
- Nested message and enum types in
Type
. - type_
db_ client - Generated client implementations.
- type_
db_ server - Generated server implementations.
- user
- Nested message and enum types in
User
. - user_
manager - Nested message and enum types in
UserManager
. - value
- Nested message and enum types in
Value
. - value_
type - Nested message and enum types in
ValueType
.
Structs§
- Annotation
- Attribute
- Attribute
Type - Authentication
- Concept
- Concept
Document - Concept
Row - Connection
- Connection
Id - Connection ID and Token are expected in all message metadata
- Database
- Database
Manager - Database
Replicas - Entity
- Entity
Type - Error
- This is an emulation of the google ErrorDetails message. Sometimes we submit ErrorDetails via the GRPC error mechanism and sometimes (in streams) we have to manually send errors
- Options
- Query
- Relation
- Relation
Type - Role
Type - RowEntry
- Server
- Server
Manager - Thing
- Transaction
- Type
- User
- User
Manager - Value
- Value
Type