This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-01
Channels
- # announcements (2)
- # aws (27)
- # beginners (67)
- # boot-dev (1)
- # cider (25)
- # cljs-dev (6)
- # clojure (192)
- # clojure-europe (1)
- # clojure-gamedev (1)
- # clojure-italy (4)
- # clojure-nl (2)
- # clojure-russia (1)
- # clojure-spec (9)
- # clojure-uk (12)
- # clojurescript (41)
- # cursive (1)
- # datomic (22)
- # figwheel-main (4)
- # funcool (1)
- # hoplon (1)
- # kaocha (11)
- # klipse (7)
- # off-topic (1)
- # overtone (1)
- # pathom (24)
- # portkey (9)
- # re-frame (129)
- # reagent (3)
- # rum (1)
- # spacemacs (1)
- # specter (6)
for storing strings larger than 4k in datomic cloud, there's a number of ways to get that wrong, I suppose..? 🙂
would this work? Generate a squuid, store the string in external storage along with that squuid, wait for external storage to report A-OK, store that squuid in datomic?
sounds better to create an unique ID every time you want to create a fact for that string, if you override the old one, and the transaction fails, then external storage and datomic is out of sync
Yeah that’s true...external storage would need immutable/accrete-only semantics then yeah? Every modification creates a new, for example, S3 object.
Right. I need an app that shocks me every time I revert back to mutable place oriented thinking.
well, I’m working on a blog-esque type app right now so these problems are at the forefront of my mind
Ping me if you make progress here, hyperfiddle is going to integrate a foreign string store soon too
will do. it’s one of my stretch goals, once I get the rest of the app up and running
i would appreciate that thank you!