Actual behavior: qbit supports only pull api to pull entities
But database should provide way to execute analytical queries - i.e. queries that allow to fetch information of custom shape, using joins and aggregate functions.
There are several approaches to consider:
1) Something sql-like - sql, jpql, cql (cassandra), gql (neo4j) etc
2) GraphQL
3) Monad comprehensions
4) Datalog
5) Something else?
It's necessary to investigate all existing approaches for querying, choose the best one and implement it.
Actual behavior: qbit supports only pull api to pull entities
But database should provide way to execute analytical queries - i.e. queries that allow to fetch information of custom shape, using joins and aggregate functions.
There are several approaches to consider: 1) Something sql-like - sql, jpql, cql (cassandra), gql (neo4j) etc 2) GraphQL 3) Monad comprehensions 4) Datalog 5) Something else?
It's necessary to investigate all existing approaches for querying, choose the best one and implement it.