This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-06
Channels
- # 100-days-of-code (15)
- # beginners (32)
- # calva (2)
- # cider (37)
- # clara (1)
- # cljs-dev (47)
- # clojure (177)
- # clojure-boston (1)
- # clojure-dev (2)
- # clojure-germany (1)
- # clojure-greece (5)
- # clojure-italy (13)
- # clojure-nl (2)
- # clojure-sanfrancisco (1)
- # clojure-uk (72)
- # clojurescript (46)
- # cursive (20)
- # datascript (7)
- # datomic (14)
- # devcards (6)
- # docker (1)
- # duct (1)
- # emacs (1)
- # figwheel (3)
- # figwheel-main (151)
- # graphql (2)
- # hyperfiddle (1)
- # interop (3)
- # jobs (3)
- # lumo (2)
- # off-topic (21)
- # pedestal (1)
- # re-frame (9)
- # reagent (25)
- # shadow-cljs (57)
- # slack-help (4)
- # specter (21)
- # tools-deps (53)
- # vim (2)
Does a transactor failover event count as "restarting it" for the purposes of what the docs recommend after doing a restore?
Yes, HA failover would work for a restore. However, I have to ask, did the “primary transactor fail during restore?
no it didn't. this is just a planning hypothetical. thanks jaret!
Hi, when I want to call a custom function (A) from within a database function (B) what is the recommended way of doing so? Should one install A as a database function and call it via invoke from within B or let B require it using :requires and call it like any other function?
Depends on whether A is on the classpath
So let's say A is not on the classpath. In this case installing the function as a database function would allow me to call it from B, right?
Ok. So, if on the other hand it is on the classpath it should be made accessible to B using :requires and call it in a "normal" fashion.
So is it recommended to split database functions into smaller functions using either of these approaches? This would be pretty neat, since a named function contributes to better readability and it could be re-used.
@U8MH51GHZ unless you have a specific reason to install database functions (e.g. managing the classpath is operationally challenging) I would prefer classpath functions. https://docs.datomic.com/on-prem/database-functions.html#classpath-functions
@U072WS7PE this is a valid reason. But this requires me to have control over the transactor (i.e. how it is started)
How does the transactor knows of a classpath function that is added to the peer? or it doesn't have to know in this case?
classpath management is up to you, put things on the classpath for processes where you need them