Fork me on GitHub

Are there any other UI options for Datomic Cloud other than REBL? I’d love to introduce non-clojure team members to Datomic to get them excited and have them try out queries, and the old Datomic Console for on-prem looked perfect, but sadly doesn’t seem to be available for cloud(?). Have people built any solutions for this need?


is there a way to configure a username and password for the Presto server built into the Datomic Cloud access gateway?


[on-prem] There is guidelines about datomic and core.async? I need to run queries inside a go-block


queries are blocking work, which you shouldn’t do in a go-block generally


unless you know they will complete very quickly?


I already locked all my threads due quering inside go-block 😕


I know, I can create a thread pool and bla bla bla But it can't be delivered as a library, like datomic.client.api.async


@U04VDQDDY I remember that sometime ago you asked about connect datomic-client-pro in a datomic:mem conn Did you end up with some solution?


@U2J4FRT2T that must have been someone else with that issue


Using clojure spec for datomic entity spec seems like a good idea. Is there any reason why it might not? I can't find it being mentioned anywhere. Doing so would make it easy to use the same verification code client side and server side. The possible downside I can think of is that it might be a bit of overhead. Something along the lines of:

(s/def :user/phone-number (s/and string? #(re-matches #"\+[0-9 +-]+" %)))
(s/def :user/uuid uuid?)
(s/def :example/user (s/keys :req [:user/uuid] :opt [:user/phone-number])

(in-ns 'example)
(defn user? [db eid]
  (let [user (d/pull db '[*] eid)]
    (if (s/valid? :example/user user)
      (s/explain-str :wavy/user user))))
;; datomic schema
{:db/ident         :example/user
 :db.entity/preds  example/user?}

Luke Schubert18:02:13

is there anyway to mass transact data?


What do you mean?

Luke Schubert18:02:56

I'm already pipelining, I was just wondering if there was some functionality to run a large batch of transactions

Luke Schubert18:02:22

I wasn't able to find anything, but I figured I would ask here in the event that I was just failing to search properly


I’m still not sure what you want more than running transactions repeatedly


there are some tricks to improve “import” transaction cost or performance if that’s what you’re looking for?


like performing the import locally on large instances with SSDs


increasing the index threshold


not indexing any attrs until the end of the import


so this is interesting! when using the standalone pull syntax with [:db/id] as the selector, the results include reverse reference attributes with a '... symbol value. is this expected?

(d/pull db [:db/id] 1234567891234)
{:attribute/a "value-a"
 :attribute/b "value-b"
 :attribute/_c ... 
 :attribute/_d ...}


I can’t reproduce this


I definitely don’t consider this expected


can you provide some more context?

Alex Miller (Clojure team)21:02:47

are you sure that's not just repl printing?



((juxt identity type) (:attribute/_c (d/pull (client/db) [:db/id] 1234567891234)))
=> [... clojure.lang.Symbol]
a coworker found this today, and i reproduced it on my machine (different IDEs and REPLs)


> can you provide some more context? DatomicCloudVersion 8846 com.datomic/client-cloud {:mvn/version "0.8.78"} and nothing peculiar about our schema. the reverse reference attributes are legit, and for what it's worth non-component. pulling * on the same entity returns the same data but without reverse references (as expected).


has anyone here successfully integrated Datomic Cloud Analytics with a third party BI platform? we can successfully validate our Presto connection, but after selecting a Schema (db name) we get the error Query failed: Expected string for :db-name someone else has the same problem and posted on the forums a few months ago without a resolution


Hey folks, how retract impact datomic performance? Make database read and write faster? What about excision, does it has the same impact or different one?