This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-15
Channels
- # announcements (2)
- # babashka (137)
- # beginners (96)
- # calva (3)
- # cider (11)
- # clj-kondo (8)
- # cljs-dev (161)
- # cljsrn (21)
- # clojure (78)
- # clojure-europe (47)
- # clojure-france (1)
- # clojure-losangeles (1)
- # clojure-nl (4)
- # clojure-spec (24)
- # clojure-uk (9)
- # clojuredesign-podcast (4)
- # clojurescript (39)
- # conjure (2)
- # core-async (27)
- # cursive (36)
- # datomic (54)
- # emacs (6)
- # figwheel (9)
- # figwheel-main (46)
- # fulcro (25)
- # graalvm (8)
- # helix (30)
- # hoplon (6)
- # hugsql (3)
- # jobs (5)
- # leiningen (7)
- # luminus (12)
- # nrepl (20)
- # off-topic (20)
- # pedestal (16)
- # re-frame (14)
- # reagent (3)
- # reitit (3)
- # remote-jobs (5)
- # rum (25)
- # shadow-cljs (60)
- # spacemacs (10)
- # vim (2)
- # xtdb (36)
Hi! Is it acceptable practice to call create-database/delete-database ~10 times per day with randomized db-name for use in functional tests in Datomic Cloud? Test cluster is separate from production one. I am just worried if this won’t lead to some kind of resource leaks over time…
as long as you’re on a recent release that should be fine @lifecoder, particularly in a separate system from prod The only thing you may need to do if you do encounter any issue is restart the compute node(s) on the system when/if you hit any issue (it is unlikely you will, there were a couple cases where it was possible on earlier versions)
Is the built-ins list for https://docs.datomic.com/cloud/query/query-pull.html#xform-option extensive? No support for int/long/double? Xforms seem like they'd make ordering card many attributes nicer. Support for clojure.edn/read-string is interesting. Implies people often store edn in a Datomic string attribute. Do people do this often?
Is qseq similar to an eduction -- passing over the data twice will recompute the result?
passing over the data twice will rerun the query
I also don’t see these documented on the client api docs. https://docs.datomic.com/on-prem/clojure/index.html
sorry for all the nits. I have a use case in my mind and I don’t have time to test with code, so I was trying to infer from docs. I want to use :xform
to get back d/entity behavior for idents
@U09R86PA4 https://docs.datomic.com/on-prem/pull.html#xform yes, you’re right it’s missing in the grammar. will fix
hard refresh doesn’t seem to fix. I also notice “q” on the on-prem “query” page is also written as if it’s for the client api
https://docs.datomic.com/on-prem/query.html#qseq says “`datomic.client.ap/qseq` utilizes the same https://docs.datomic.com/on-prem/query.html#grammar.” Both are client api. Maybe by design I’m thinking now
https://docs.datomic.com/on-prem/pull.html#xform talks about resources/datomic/extensions.edn
and whitelisting functions--I’m not aware of that being an on-prem thing?
https://docs.datomic.com/on-prem/index-pull.html looks like a client api and mentions client options--maybe it is actually the same as peer
I’m more excited about walking an index in reverse than index-pull’s other features. I’m not sure index-pull makes sense in on-prem otherwise
> Enhancement: Improve internal record keeping of active databases that could lead to spurious error messages. Does this fix https://support.cognitect.com/hc/en-us/requests/2598?
Naming question:
Why does :xform
is named in this way?
clojure.core/sequence
for example has a xform coll
signature, where xform
means functions like clojure.core/cat
, not clojure.core/str
I mean, I know that datomic and clojure are "independent" products, but I also know that the ideas behind both are the same
What does xform
means?
I was also curious about this. I usually think of "xform" as a transducer. Datomic's xform is not a transducer, afaict.
random newb question: Can Datomic use Foundation DB as its durable storage?
does Foundation DB have a JDBC driver?
Unfortunately, it does not. There is an fdb-client
that is required to be installed on every box. However, we would consider writing one for FDB if that is the only criteria for plugging it into Datomic.
We (my company is http://novolabs.com) are going to be adopting Datomic for our operational DB. We use FDB for our historical data and would love to have Datomic use FDB for its durable storage as we would only need one storage solution which would greatly improve our SRE.
Obviously we don't test against the (not yet written) driver 🙂 but anything that correctly implements the JDBC spec (particularly transaction isolation) should work fine as a Datomic storage service. On the standard license, we would be able to support you with Datomic but not with any FDB-specific issues.
Understood. Thanks for the help and I’ll let you know if/when we have a JDBC driver for FDB that is ready for general consumption.