This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-18
Channels
- # announcements (6)
- # babashka (16)
- # beginners (194)
- # calva (20)
- # cider (34)
- # clj-kondo (38)
- # clojure (89)
- # clojure-europe (10)
- # clojure-finland (15)
- # clojure-italy (2)
- # clojure-nl (15)
- # clojure-sg (7)
- # clojure-spec (15)
- # clojure-uk (86)
- # clojurebridge (1)
- # clojurescript (60)
- # community-development (11)
- # conjure (13)
- # core-async (48)
- # core-typed (3)
- # cursive (22)
- # datascript (8)
- # datomic (40)
- # duct (11)
- # emacs (3)
- # figwheel-main (22)
- # fulcro (45)
- # graphql (1)
- # helix (9)
- # hoplon (15)
- # hugsql (7)
- # jobs-discuss (47)
- # juxt (7)
- # kaocha (21)
- # luminus (1)
- # malli (13)
- # meander (2)
- # off-topic (52)
- # parinfer (19)
- # re-frame (66)
- # reagent (1)
- # reitit (3)
- # ring-swagger (1)
- # rum (2)
- # shadow-cljs (72)
- # spacemacs (5)
- # sql (4)
- # timbre (5)
- # tools-deps (15)
- # vim (5)
- # vrac (7)
Hi, I noticed that datascript connections have additional key-values like
{
:schema {}
:eavt #{ }
:aevt #{ }
:avet #{ }
:max-eid 0
:max-tx 536870912
:rschema { }
:hash #object[cljs.core.Atom {:val 0}]
}
I’m able to access them with the keyword, but when I prn
the connection, I only see
#datascript/DB{:schema {}},
:datoms []}
Does this have something to do with the fact that datascript DBs are records?yeah, the db type has a custom IPrintWithWriter
implementation which defines how its printed
it doesn’t print what the actual object is - those are internal details - but rather an opaque description of what’s in the DB
the nice thing about this is that datascript defines reader literals for #datascript/DB
, so you can prn
a DB and send it over a remote connection
wow, thanks so much @lilactown x2