Nikolas Göbel
Nikolas Göbel
It is currently not possible to use aggregations within rules, because they can only appear within the find specification. It should be possible to use aggregations like transforms: ```clojure [[(total...
Something like `[:find (truncate ?t) :where ...]` currently requires an extra clause `[:find ?trunc :where [(truncate ?t) ?trunc] ...]` which is not as nice as it could be.
We should add support for constant bindings in ... - [x] predicates - [x] function expressions - [ ] rule expressions For predicates and function expressions support is rather straight-forward,...
Also known as _blanks_ in Datomic (https://docs.datomic.com/on-prem/query.html). Trailing blanks are also optional and should be elidable.
Currently, only fixed-arity rules are supported. It would be nice to support rule definitions with different arities, to be fully compatible with Datomic in this regard.
Some aspects of a query can be checked locally during parse-time, e.g. that constants are of the correct type, attributes and rules exist, rule and query names don't clash with...
- [ ] Split `CardinalityOne` into `LWW` and `FWW` - [ ] CAS - [x] Rename `CardinalityMany` -> `Distinct` - [ ] implement on top of streams / arrangements where...
We should split up `RegisterSource` in the same vein as `RegisterQuery` + `Interest`. This would allow us store source configurations and either synthesize them in combination with a query or...
It would be nice to be able to use the library with a custom Value type.
Some relations (such as Datomic's `:db/ident`, or relations carrying metadata) are comparatively small but can induce massive skew, especially once reverse indices are involved. This can lead to straggling workers...