Is your feature already requested in another issue?
No.
Is your feature a defect?
No.
Is your feature request related to a problem? Please describe.
The kinds of statements supported by RIDDL all pertain to sending messages, a few logic statements, and housekeeping things. None of them are specific to data storage. This needs to be enhanced in the case of a Repository.
Describe the solution you'd like
Issue #594 detailed some things for Projectors that should have been targeted towards Repositories. Translating those requests, we arrive at these data storage statement capabilities:
Statements to define the schema of the storage, for any model (relational, graphical, time series, document, etc.). This needs to use RIDDL's type system to define the data schema structurally.
Statements to modify the storage: create, update, insert, append, remove
Statements for reading the storage: read, query
Statements for creating indices of various (abstract) kinds
Statements for putting values into indices
for example; create record Table1Fields with index Table1Fields.id
Statements or statement clauses that do their operational conditionally based on boolean expression
Partial updates to record/node/document/etc.
Describe the alternatives you've considered
None have been considered, but there are constraints to this. We do not want to implement a generalized and complicated language like SQL that deals with every kind of data structure. That would render RIDDL into a class of programming languages instead of a design language. The use of abstract constructs should be used so there's a large freedom of expression in natural language.
Is your feature already requested in another issue?
No.
Is your feature a defect?
No.
Is your feature request related to a problem? Please describe.
The kinds of statements supported by RIDDL all pertain to sending messages, a few logic statements, and housekeeping things. None of them are specific to data storage. This needs to be enhanced in the case of a Repository.
Describe the solution you'd like
Issue #594 detailed some things for Projectors that should have been targeted towards Repositories. Translating those requests, we arrive at these data storage statement capabilities:
create record Table1Fields with index Table1Fields.idDescribe the alternatives you've considered
None have been considered, but there are constraints to this. We do not want to implement a generalized and complicated language like SQL that deals with every kind of data structure. That would render RIDDL into a class of programming languages instead of a design language. The use of abstract constructs should be used so there's a large freedom of expression in natural language.
Additional Context
None.