This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-12-11
Channels
- # adventofcode (31)
- # announcements (6)
- # babashka (5)
- # beginners (93)
- # calva (15)
- # cider (20)
- # cljs-dev (16)
- # clojure (159)
- # clojure-berlin (1)
- # clojure-dev (5)
- # clojure-europe (9)
- # clojure-italy (9)
- # clojure-losangeles (2)
- # clojure-nl (26)
- # clojure-spec (7)
- # clojure-uk (33)
- # clojurescript (54)
- # clojutre (5)
- # cursive (20)
- # datomic (23)
- # emacs (19)
- # events (1)
- # expound (1)
- # figwheel-main (1)
- # fulcro (104)
- # hyperfiddle (1)
- # jobs (1)
- # luminus (10)
- # malli (59)
- # nrepl (1)
- # off-topic (11)
- # pathom (5)
- # planck (15)
- # reagent (13)
- # reitit (8)
- # rewrite-clj (10)
- # ring-swagger (3)
- # shadow-cljs (129)
- # tools-deps (46)
- # xtdb (14)
- # yada (1)
So, this is now a open question :) https://clojurians.slack.com/archives/C03RZMDSH/p1575947979130900 What are the most favourite DBs for Clojure ecosystem and community in general?
The other day I was having an issue with running the transactor and console on windows due to java classpath sizes and I found a super simple solution so I wanted to drop it here in case it's useful for anyone else
as of java 6 cp supports wildcards so you can remove the two for loops in ./bin/classpath.cmd
and replace them with SET CP_LIST="bin;resources;lib/**;datomic-transactor*.jar"*
Hi! I'm kinda noobie on datomic, does anyone know the difference between "Production" and "Production 2" Topologies??
@adrian169 that is an artifact of AWS Marketplace issues You should use whichever contains the latest release
Also, I don't really know how to configure instances so they are not i3.large
Ohhhhh thanks!
Hmmm isn't there a way to use smaller instances
on production?
Thank you so much!
Is there a way to directly omit the :db/ident
key in a pull
expression for an "enum"? having only its value returned
just used update
for this simple case, definitely going to need clojure.walk on the next one, thanks
I’m having trouble with upserts on entities with tuple identities containing a ref
. The only way I can get upserts to work is to look up the entity id of the ref and use that in the query. Tempids work for the initial insert but then fail with an identity conflict. Lookup refs don’t work at all. And tuple
does not appear to work in transact
. Here’s a repro script:
(d/transact dt-conn {:tx-data [{:db/ident :example/r
:db/valueType :db.type/keyword
:db/cardinality :db.cardinality/one
:db/unique :db.unique/identity}
{:db/ident :example/id
:db/valueType :db.type/string
:db/cardinality :db.cardinality/one}
{:db/ident :example/ref
:db/valueType :db.type/ref
:db/cardinality :db.cardinality/one}
{:db/ident :example/multi
:db/valueType :db.type/tuple
:db/tupleAttrs [:example/ref :example/id]
:db/cardinality :db.cardinality/one
:db/unique :db.unique/identity}]})
(d/transact dt-conn {:tx-data [[:db/add "one" :example/r :one]]})
(d/transact dt-conn {:tx-data [{:example/ref [:example/r :one]
:example/id "foo"}]}) ; Succeeds once - Fine, need to include the identity tuple
(d/transact dt-conn {:tx-data [{:example/ref [:example/r :one]
:example/id "bar"
:example/multi [[:example/r :one] "bar"]}]}) ; Fails - "Invalid tuple value"
(d/transact dt-conn {:tx-data [[:db/add "ONE" :example/r :one]
{:example/ref "ONE"
:example/id "baz"
:example/multi ["ONE" "baz"]}]}) ; Succeeds once. Then fails - "Unique conflict: :example/multi, value [...] already held by ..."
(d/q '[:find ?e :where [?e :example/r :one]] (d/db dt-conn)) ; Put the resulting id in the next query
(d/transact dt-conn {:tx-data [{:example/ref [:example/r :one]
:example/id "qux"
:example/multi [<insert value here> "qux"]}]}) ; Succeeds upsert
Any suggestion on how to make this work?I'm getting " handshake timed out" when connecting to a datomic free transactor using the datomic clojure client api:
Dec 11, 2019 9:18:41 PM org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector createConnection
ERROR: AMQ214016: Failed to create netty connection
javax.net.ssl.SSLException: handshake timed out
at io.netty.handler.ssl.SslHandler.handshake(...)(Unknown Source)
I vaguely recall there being some changes to all this, but I don't remember the detail.Q: I’m running Ions using the “connect on use” pattern when my app startup calls a component/start of my stack. My stack becomes unstable after a few CI deploys and I suspect that the lack of a component/stop call before the new stack is started is leaking resources such as aws clients. What is the recommended way to shutdown stacks during deploys? Is there a hook in one of the step functions used in deploy to address this?