This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-12
Channels
- # beginners (47)
- # boot (5)
- # bristol-clojurians (1)
- # cider (45)
- # clara (2)
- # cljs-dev (11)
- # cljsrn (47)
- # clojure (169)
- # clojure-brasil (2)
- # clojure-dusseldorf (22)
- # clojure-finland (1)
- # clojure-italy (9)
- # clojure-nl (3)
- # clojure-poland (2)
- # clojure-russia (4)
- # clojure-spec (79)
- # clojure-uk (105)
- # clojurescript (59)
- # core-async (41)
- # cursive (31)
- # datomic (10)
- # devcards (1)
- # duct (6)
- # editors (9)
- # emacs (12)
- # figwheel (1)
- # fulcro (50)
- # java (4)
- # mount (1)
- # off-topic (47)
- # onyx (33)
- # pedestal (1)
- # protorepl (1)
- # re-frame (32)
- # reagent (45)
- # ring-swagger (6)
- # shadow-cljs (100)
- # tools-deps (6)
- # uncomplicate (27)
- # vim (3)
I need some predicate functions like ref?
to-many?
, that check if a keyword is or not a ref?
on db.
Is a good idea create a mem db at build-time, install schema, run a query, get the list of idents/keywords and make this functions
Or is better do it at runtime, with memoize or something like?
This seems a trivial predicate to write with d/attribute
. Why are you thinking of caching, memoizing, etc?
there is no d/attribute on client API https://docs.datomic.com/cloud/client/client-api.html
peer API is way better then client API but client API is tons of light years better then #sql 🙂
Not sure about "better", but I actually query my "model map" which contains attribute descriptions (and which get turned into schema change txs at system boot).
I actually have a number of phantom attributes, too, that get computed but never committed, and this structure has made that possible.
Hey all, I'm having a bit of trouble trying to get a Lambda function connected to my Datomic Cloud db via the client API. My function keeps timing out with the following error:
Unable to execute HTTP request: Connect to
...
connect timed out
I've followed the instructions here: https://docs.datomic.com/cloud/operation/access-control.html
And here: https://docs.datomic.com/cloud/operation/client-applications.html
but still not having any luck 😕
My Lambda is configured to access the Datomic VPC via security group $(SystemName)-apps
as in the documentation. I have not tried VPC Peering however. Is that a necessary step when trying to access Datomic Cloud from Lambda? Thanks.