Skip to content
This repository was archived by the owner on Sep 12, 2018. It is now read-only.

Milestones

List view

  • No due date
    0/28 issues closed
  • No due date
    1/2 issues closed
  • This milestone covers description, maintenance, and use of materialized views and in-memory caches.

    No due date
    0/1 issues closed
  • This milestone encompasses a variety of datatypes that might be stored in Mentat: - Timestamps, UUIDs, interned keywords, bignums, and URIs — Datomic parity. - JSON, which will be particularly useful for JS consumers, and opens the door to JS-aware predicates and destructuring. - Geospatial data, using [RTree](http://www.sqlite.org/rtree.html) or SpatiaLite.

    No due date
    4/10 issues closed
  • Mentat stores a sequence of changes. That makes replication and synchronization more tractable than stores that only maintain the current state of the world. This milestone defines the ability for a Mentat store to be _replicated_ from a primary to a secondary, and for two or more stores to be _synchronized_ via a centralized clearing-house.

    Overdue by 7 year(s)
    Due by September 30, 2018
    5/10 issues closed
  • One of our core value propositions is exposing the transaction log to applications. This entails a bunch of query work to allow individual statements and the query as a whole to examine the transaction log or a historical version of the database, and a little core work to allow callers to work with database instances.

    No due date
    0/2 issues closed
  • This extends basic feature completeness to encompass excision, `noHistory`, import and export, schema evolution and migration, logging, documentation, asynchronous writes, concurrent read isolation, and query preparation/caching

    Overdue by 7 year(s)
    Due by June 30, 2018
    7/36 issues closed