This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-06-21
Channels
- # announcements (9)
- # beginners (222)
- # boot (11)
- # calva (40)
- # cider (1)
- # clj-kondo (10)
- # cljs-dev (1)
- # cljsrn (8)
- # clojars (4)
- # clojure (50)
- # clojure-dev (4)
- # clojure-ecuador (1)
- # clojure-europe (4)
- # clojure-italy (3)
- # clojure-madison (2)
- # clojure-nl (26)
- # clojure-spec (86)
- # clojure-uk (34)
- # clojurescript (11)
- # clr (1)
- # cursive (46)
- # datomic (19)
- # emacs (4)
- # events (1)
- # fulcro (22)
- # graalvm (4)
- # graphql (2)
- # jobs-discuss (40)
- # leiningen (10)
- # luminus (6)
- # nrepl (7)
- # off-topic (18)
- # onyx (6)
- # overtone (1)
- # pedestal (2)
- # planck (1)
- # re-frame (5)
- # reagent (3)
- # reitit (8)
- # rewrite-clj (2)
- # shadow-cljs (139)
- # sql (4)
- # tools-deps (42)
A demo of using Metabase with Datomic, using the newly developed metabase-datomic driver https://youtu.be/6eLME2TZ7oU


@U07FP7QJ0 This is great, thank you!
1. does it still need an SQL connection to save dashboards etc or does it use datomic to store the config as well?
2. I’m using Datomic Cloud i.e. client API. I would be interested in testing/porting your work to the client API. has anyone else expressed interest in this?
1. Yes, You still need a database for metabase's own data. Typically h2/mysql/postgres. 2. So far this has been developed for a single client and uses the peer API. I can imagine there would be interest in using it with datomic cloud.
Driver source and more info: https://github.com/lambdaisland/metabase-datomic
nREPL 0.7 gains native EDN transport https://metaredux.com/posts/2019/06/21/nrepl-0-7-introducing-a-native-edn-transport.html


