This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-09
Channels
- # babashka (63)
- # beginners (97)
- # biff (11)
- # chlorine-clover (5)
- # cider (46)
- # clara (2)
- # clj-kondo (34)
- # clojure (65)
- # clojure-austin (1)
- # clojure-europe (9)
- # clojure-france (10)
- # clojure-italy (11)
- # clojure-nl (3)
- # clojure-spec (29)
- # clojure-uk (5)
- # clojuredesign-podcast (1)
- # clojurescript (56)
- # clr (6)
- # component (17)
- # conjure (5)
- # core-typed (5)
- # cursive (23)
- # data-science (5)
- # datahike (3)
- # dirac (3)
- # emacs (20)
- # fulcro (17)
- # graalvm (10)
- # graphql (8)
- # helix (99)
- # honeysql (7)
- # jobs-discuss (9)
- # juxt (9)
- # leiningen (14)
- # malli (3)
- # meander (6)
- # off-topic (77)
- # pathom (7)
- # re-frame (12)
- # reagent (8)
- # reitit (10)
- # restql (1)
- # shadow-cljs (22)
- # spacemacs (10)
@whilo It looks like my issue from a few days ago where the db wasn’t serialized to the file was because I used transact
from the core ns not the api ns…
Which brings me back to this question.
Are you planing to put every public function in datahike.api?
Asking because I use db?
and conn?
from datahike.core for specs and therefore I am sometimes require only core, only api or both.
Yes, that is unnecessarily confusing, we plan to have one unified namespace. @konrad.kuehne is working on this, we will probably cover the same functions as exposed in datomic.client.api
to reduce friction with Datomic users.
In general you should not use datahike.core
, @konrad.kuehne can we expose these predicates in the api as well?