Local Dev and CI with dev-local

By default, dev-local stores all databases under a common storage directory. To specify this directory, create a .datomic/dev-local.edn file in your home directory, containing a map with :storage-dir and an absolute path:

{:storage-dir "/full/path/to/where/you/want/data"}

When you request dev-tools, your download email also includes instructions for adding the dev-tools maven repository to your project.

datomic-samples is a set of databases that are used throughout these Datomic docs and the Day of Datomic tutorials. To install the datomic samples on your local computer:

• Get dev-local.
• Download the latest (2020-07-10) datomic-samples.zip.
• Unzip the datomic-samples zip into your storage dir.

You can connect and use them by setting your dev-local system name to "datomic-samples":

(require '[datomic.client.api :as d])
(def client (d/client {:server-type :dev-local
                       :system "datomic-samples"}))
(d/list-databases client {})
=> ["mbrainz-subset" "solar-system" "social-news" "movies" ...]

Diverts subsequent d/client calls for system to local storage. arg-map has the following keys:

Closes the connection to a database and releases the memory used by it. Values of that database can no longer be used. arg-map has the following keys:

Import a Datomic Cloud database into dev-local. arg-map has the following keys:

A filter spec has the following keys, all optional:

:include-attrs keys are either fully-qualified attribute names or a namespaced keyword with * as a name (includes all attrs in namespace, e.g. :order/*).

:include-attrs filters are maps with optional :before and :since keys limiting the time range for attributes as per before/since above.

Schema attributes are always included. When a filter spec is present:

• All other attributes must be included explicitly.
• Excludes take precedence over includes.

You can re-import to get more recent data if you have not transacted locally. You cannot import to a database that currently has an open connection.

The following example imports a customer database, including

• all schema
• all history of customers (except their secrets!)
• orders since May 2020

(dl/import-cloud
 {:source {:system "customers"
           :db-name "customers"
           :server-type :ion
           :region "us-east-1"
           :endpoint "https://ljfrt3pr18.execute-api.us-east-1.amazonaws.com"}
  :dest {:system "production-imports"
         :server-type :dev-local
         :db-name "customers-and-recent-orders"}
  :filter {:include-attrs
           {:customer/* {}
            :order/* {:since #inst \"2020-05\"}}
           :exclude-attrs [:customer/secret]}})

• Upgrade Client to 1.0.126

• Upgrade Client to 1.0.125

• Enhancement: The datalog engine will now do self-unification within a single clause.

• Use latest Client
• Fix anomaly where Attr-spec's for boolean attributes with false values failed

• Improvement: enable BigInt fressian handler

• New: Change the scale of a BigDecimal attribute in a transaction.
• Improvement: Better error messages for import-cloud.
• Fix: Query correctly treats range functions as functions (not as predicates).

• New feature Memdb
• Improvement: Increase the limit on the total number of datoms in a transaction imported with import-cloud to 16 million.
• Improvement: Increase the limit on the length of strings imported with import-cloud to 1 million characters

• Provide dev-tools via Cognitect maven repo

• Improvement: better error message when calling a function that is not in the :allow list of datomic/ion-config.edn

• Update: use latest Client API

• Enhancement: Reread the deps-local.edn config file when creating a client.
• Enhancement: Provide better feedback while loading and importing databases.
• Enhancement: Update client documentation about connecting to dev-local systems

Initial Release