This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-03-02
Channels
- # announcements (9)
- # babashka (67)
- # beginners (62)
- # bitcoin (2)
- # clara (1)
- # clj-kondo (62)
- # cljfx (6)
- # cljs-dev (25)
- # clojars (17)
- # clojure (142)
- # clojure-australia (2)
- # clojure-europe (42)
- # clojure-gamedev (2)
- # clojure-nl (31)
- # clojure-poland (10)
- # clojure-spec (14)
- # clojure-uk (30)
- # clojurescript (3)
- # conjure (1)
- # cursive (10)
- # data-science (1)
- # datascript (4)
- # datomic (9)
- # depstar (7)
- # fulcro (17)
- # girouette (15)
- # graalvm (44)
- # honeysql (20)
- # jackdaw (3)
- # jobs (8)
- # jobs-discuss (10)
- # juxt (5)
- # lein-figwheel (1)
- # lsp (175)
- # malli (19)
- # pedestal (2)
- # reagent (31)
- # reitit (2)
- # remote-jobs (3)
- # reveal (12)
- # sci (77)
- # shadow-cljs (22)
- # specter (6)
- # startup-in-a-month (2)
- # tools-deps (1)
- # xtdb (21)
disclaimer: not totally sure what I'm talking about. Datascript is intended for in-memory stuff so that logic to live client-side, probably whilst using a different db on the backend. There are other options if durability is required, there's a good summary at the very bottom of this page: https://github.com/juji-io/datalevin
wrt datomic compatibility, datascript's own docs cover it in detail here: https://cljdoc.org/d/datascript/datascript/1.0.4/doc/readme I'm well over my skis in this assertion but the schema differences, lack of typesystem in datascript and lack of db/ident in my limited experience mean that code fragments from datomic don't always port, I believe in a large project you''d be able to paper over it
hard to say whether you need datalog, I'd rather chew off my own arm than write any more SQL though
I 2nd this arm chewing statement