This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-02-07
Channels
- # aleph (1)
- # beginners (152)
- # cider (26)
- # clara (2)
- # cljs-dev (13)
- # cljsrn (5)
- # clojure (198)
- # clojure-greece (15)
- # clojure-italy (39)
- # clojure-sanfrancisco (3)
- # clojure-spec (28)
- # clojure-uk (16)
- # clojurescript (52)
- # community-development (15)
- # core-async (26)
- # cursive (42)
- # data-science (28)
- # datomic (19)
- # devops (7)
- # duct (11)
- # emacs (24)
- # fulcro (22)
- # garden (4)
- # leiningen (12)
- # luminus (1)
- # mount (5)
- # off-topic (106)
- # om (5)
- # onyx (10)
- # parinfer (37)
- # re-frame (17)
- # reagent (47)
- # shadow-cljs (36)
- # yada (2)
Topological question. I have a server with datomic on it. It has a transactor and a mysql running as the only services. When connecting from a peer, I specificy only the mysql ip and port, but not the transactors. Is it even used then? The transactor I mean
@laujensen yes. peers discover transactor details from storage; this is how high-availability works (transactors heartbeat into storage)
How do you go about giving your coworkers access to the Peer library without giving them your http://my.datomic.com credentials?
ah nevermind, bin/maven-install
was really what I was after.
I know several of our clients with large teams keep their datomic account on an “<mailto:[email protected]|[email protected]>” shared e-mail. If you find you need something like that let me know and I can update your technical contact information/issue a password reset.
Thanks @U1QJACBUM, the problem I see with that approach is that each time a developer leaves the company I will probably have to change the credentials :s
@laujensen https://docs.datomic.com/on-prem/schema.html#altering-nohistory-attribute
is there a way to do something like clojure's ensure
in cloud? I can use :db.fn/cas
with the same value, except when value is nil
no-history attr, assert it on an entity with a value; assert a new value at end of tx, update with db.fn/cas. lets you do optimistic locking
interesting idea, will test it out
I have a rule with multiple definitions and one output variable. It looks like: [(references-somewhere ?scope ?referencee ?referencer) [?scope ?a ?referencee] [?a :db/isComponent false] [?a :db/valueType :db.type/ref]] [(references-somewhere ?scope ?referencee ?referencer) [?referencer ?a ?referencee] [?a :db/isComponent false] [?a :db/valueType :db.type/ref] (descendant ?referencer ?scope)] I can't figure out what syntax to use in that first definition to indicate that ?referencer should be bound to the value of ?scope. Can someone help me out?