eva
eva copied to clipboard
Workiva
A distributed database-system implementing an entity-attribute-value data-model that is time-aware, accumulative, and atomically consistent
Datomic introduced the ability to allow certain portions of transaction data to be inferred with their client API. https://docs.datomic.com/cloud/transactions/transaction-data-reference.html#implicit-tempids Notably, cognitect has formalized around a grammar for the transactions: https://docs.datomic.com/cloud/schema/schema-reference.html...
The peer-isolated "wait until I can provide a snapshot at t" version of sync.
A few builtin predicate or binding expressions are missing, there are not custom implementations of some of the builtin functions like `+`
Right now we send the entire transaction log entry to the Peer that submit a transaction when the transactor performs its directed response. We should remove this part of the...
```clj (def conn (connect {:local true})) (def schema [{ :db/id #db/id[:db.part/db] :db/ident :example.schema/exampleRef :db/valueType :db.type/ref :db/isComponent true :db/cardinality :db.cardinality/one :db.install/_attribute :db.part/db :db/doc "Example"}]) @(transact conn schema) (datoms (db conn) :vaet...
This is a pretty minor optimization, but when there are multiple pull specs being used as aggregates in the query engine, we could evaluate the pulls simultaneously.
Internally, during a pull evaluation, generated subframes may be duplicated an arbitrary number of times. Consider the spec `[{:ref [*]}]` being evaluated on 10000 distinct entities which all have a...
This involves a few moving pieces: 1. The transactor should have a default timeout for killing long-running transactions so that we can protect liveness of the logical instance in the...
There exists a ton of recent (and not so recent) literature on powerful ways to build, optimize, and utilize database query engines. This issue is a place to collect references...