This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-09-28
Channels
- # admin-announcements (1)
- # announcements (1)
- # beginners (17)
- # boot (29)
- # cider (8)
- # clojure (87)
- # clojure-czech (2)
- # clojure-nl (2)
- # clojure-russia (108)
- # clojurebridge (9)
- # clojurescript (34)
- # cursive (5)
- # datascript (15)
- # devcards (14)
- # editors (6)
- # hoplon (121)
- # jobs (7)
- # ldnclj (22)
- # onyx (2)
- # re-frame (31)
- # reagent (43)
- # testing (2)
So happy to have found this channel.
I want to use the datom diffs in a transaction report to update datascript running on nodejs. Is that possible to do directly, or do I need to parse the datoms into :db/adds?
[3 :project/title “title” 123456 false] [3 :project/title “new title” 123457 true]
into [:db/add 3 :project/title “new title”]
Looks like init-db
might be useful, but not sure that’s the right way to go about it.
My goal is to avoid using datomic, and to sync browser clients via datascript on nodejs.
If you don't have other data in the db than the datoms you're loading, init-db
works well
I do have the last sync of the db from the browser. So I’d be merging those new datoms into a pre-existing db.
I don’t want to hack datascript to include the ds query in the metadata for the tx-report, but that seems the cleanest route.
So you think transacting the transformed diffs (parsing them into :db/adds) would be the way to go?
Does datascript doesn’t keep the false
datoms?
I know it does some sort of cleaning, to keep memory down, but I don't know the details
I suppose it wouldn’t matter if I’m parsing it into :db/add.