This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-02-06
Channels
- # bangalore-clj (2)
- # beginners (55)
- # boot (32)
- # bristol-clojurians (4)
- # cider (16)
- # clara (13)
- # cljsrn (6)
- # clojure (110)
- # clojure-india (1)
- # clojure-italy (69)
- # clojure-spec (32)
- # clojure-uk (15)
- # clojurescript (102)
- # community-development (6)
- # cursive (1)
- # datomic (9)
- # docs (2)
- # duct (1)
- # emacs (39)
- # events (3)
- # fulcro (131)
- # garden (1)
- # immutant (4)
- # jobs (1)
- # jobs-discuss (5)
- # keechma (1)
- # lein-figwheel (6)
- # leiningen (6)
- # mount (6)
- # nrepl (2)
- # off-topic (69)
- # om (54)
- # parinfer (7)
- # re-frame (63)
- # reagent (13)
- # remote-jobs (1)
- # shadow-cljs (90)
- # spacemacs (8)
- # specter (6)
- # sql (16)
- # testing (1)
- # unrepl (3)
- # vim (4)
- # yada (1)
I have a database which has many reads and very few writes. Can I expect my proof of concept project build on top of datomic:mem:// to have similar performance than a production instance built sitting on top of postgres?
Hi all, I am trying to understand the current state of non-jvm language interop with datomic. In the datomic documentation it is stated that the REST API is deprecated and is advised to use the client API instead. As far as I can see, there is no spec on how to implement a Client API in another language, nor are their any existing implementations (other than the clojure one). Am I correct in assuming that the client API is an ongoing development and the correct way of doing non-jvm interop is to still use the REST API?
Is it possible or even advisable to use something like juxt/tick with datomic, or should I just stick with clojure.instant?
Can you elaborate a bit on how you would use juxt/tick and how that relates to Datomic? Datomic’s :db.type/instant maps to instances of java.util.Date. Tick is using java.time.Instantwhich needs to be coerced into java.util.Date. If you are interested in using tick.interval/Interval, you would have three options: 1) reference to an entity constructed from the interval, or 2) serialize it as string, or 3) serialize it as bytes (`:db.type/bytes`).
Is there a GDPR solution for datomic cloud? Something along the lines of excision
Yeah i've read that message, but we are currently on on-premise datomic and are considering cloud but this would be a blocker
@stuarthalloway - it may be beneficial for Datomic Cloud if you talk on your intentions to support excision or similar; the new EU regulations, known as GDPR, are due to be fully complied by in mid May this year, with harsh punishment for non-compliance. it may prevent DCloud adoption for some folks who would otherwise jump in with both feet and eyes closed, if they can’t check this box for their exco 🙂