@gdeer81, yes, I think that as well but also just how to work with it from the app

@aramz well if you're talking about a Clojure app, you're in luck because Datomic queries just return data and Clojure is great with data. If you're using Clojurescript as the frontend then you're also in luck because it too likes data. I have a Datomic project I started and abandoned three years ago that might give you just enough of a jumping off point to get you feet wet. Fork https://github.com/gdeer81/functional-pharmacy and look at the schema and the different namespaces and the queries that are in there and see if you can build a UI for it or enhance the back end. When I demo'd that app I was literally just evaluating forms inside of emacs to show people at work how Datomic worked. If you want to take it to the next level you can, or you can just use it as a poor man's reference app

datalog-rules: utilities for managing Datalog rulesets in Clojure. https://github.com/vvvvalvalval/datalog-rules

@gdeer81 thank you, going to checkout the project. Have you been working with datomic since that project?

I'm sorry if this is too basic of a question but i've just recently gotten into Clojure (and looking into datomic). I understand that datomic focuses on data over time among others. But could somebody give a brief description of why they chose datomic over i.e. postgres?

really recommend any of Rich Hickeys talks on that, @wilcov

he says it best

Thanks @robert-stuttaford I've found 'intro to datomic' by him, i'll have a look at that

@wilcov watch em all 🙂 http://docs.datomic.com/videos.html

this one may answer the questions you have http://channel9.msdn.com/posts/Rich-Hickey-The-Database-as-a-Value

and if you’re going all the way down the rabbit hole, http://www.datomic.com/training.html

@wilcov: datomic can use postgres as the underlying storage. Some trivia though: if you read the original postgres paper (or maybe ingres paper, can't recall), one of the main aims was tracking changes over time. And they had it, though no idea how it worked. But they removed it at a certain point in time.

http://db.cs.berkeley.edu/papers/ERL-M91-62.pdf

Section 4

I guess if you turn off vacuuming, you can get some time travel possibility within Postgres.

Looks like the console doesn’t update its view of the db until I refresh the page. Is this normal?

https://eng.uber.com/mysql-migration/ this outlines how Postgres internals is append only too.