Database under version control?

Hi all,
as you may know, I am quite fond of writing small Clojure command-line tools for a lot of my things. Lately, I started using a sqlite database for small things that I need to track (thousands of records) and I store it under git. So whatever happens, I have the backup and/or I can go back in time. Works well and I feel safe.

What I don’t like, of course, is that the database is a binary blob. So I was thinking, why not just storing a trivial EDN file? I don’t care about performance, and whatever I can do in SQL I can do in Clojure.

Anybody else went down my same rabbit hole? :slight_smile:

Not exactly what you want, but somewhat related:

Still stores the database as a binary blob.

1 Like

Duratom gives you the ability to use a file backed atom that can store as plain edn:

It can be treated exactly as a normal clojure atom.
Note that this means you will not be able to do complex queries like you can in sqlite.

(I’ve messed around with sticking this atom behind datascript to try to get the best of both worlds which works ok)


The Duratom looks very much like what I had in mind. I’ll give it a go! :sunny:

There is also It has file persistence baked in, and support for various other types of persistent storage if you need it.

Disclaimer: I’m writing a PR which adds redis as a possible durable storage.

Another exciting development: GitHub - replikativ/datahike: A durable Datalog implementation adaptable for distribution.
Like DataScript, but durable. Still, not suitable for storing the DB directly as pretty printed EDN, but it has an import/export mechanism which allows you to store the datoms under version control. You could run the import on application startup and hook up the export as a pre-commit hook. You get to use datalog as your query language which is awesome.


Datahike sounds really cool! Thanks for bringing it to attention here.

Hi. The main author of datahike here. Some clarifications:

  1. datascript can already be serialized, if efficiency is no concern. The only constraint is that all data needs to fit in memory.

  2. datahike supports the same functionality, but this obviously requires to at least hold all data of the edn-serialization in memory (well, you can do reading so that even this is not necessary). Additionally datahike provides the mentioned line-based export and import feature for the EAVT index.

  3. The right way to do it imo is to snapshot the database. Datomic does this automatically with its as-of history capabilities. It is not hard to implement, since datahike already uses persistent datastructures on disk (hitchhiker-trees). The easiest way atm. is to manually copy the :db key (which contains the database) from the underlying konserve store (filestore/leveldb) to some history (e.g. a separate konserve append-log) after you have called transact.

I still need to sort out the history stuff and improve the datahike implementation. If somebody is interested in helping out, feel free to join.


This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.