This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # beginners (6)
- # calva (1)
- # cider (17)
- # clj-kondo (10)
- # clojure (4)
- # clojure-austin (3)
- # clojure-spec (3)
- # clojurescript (40)
- # clojurex (17)
- # core-async (10)
- # cursive (1)
- # data-science (2)
- # datomic (15)
- # emacs (10)
- # fulcro (15)
- # funcool (1)
- # graalvm (15)
- # joker (3)
- # nrepl (34)
- # off-topic (10)
- # pedestal (3)
- # rewrite-clj (6)
- # spacemacs (5)
- # sql (11)
https://www.dcc.fc.up.pt/~ricroc/homepage/publications/leap/2013-WFLP.pdf > A Datalog Engine for GPUs > Abstract. We present the design and evaluation of a Datalog engine for execution in Graphics Processing Units (GPUs). The engine eval- uates recursive and non-recursive Datalog queries using a bottom-up approach based on typical relational operators. It includes a memory management scheme that automatically swaps data between memory in the host platform (a multicore) and memory in the GPU in order to reduce the number of memory transfers. > To evaluate the performance of the engine, three Datalog queries were run on the engine and on a single CPU in the multicore host. One query runs up to 200 times faster on the (GPU) engine than on the CPU. any likelihood this will ever be relevant to Datomic?
Is it a good idea or even possible for entity attributes to have names that are integrated with spec? So something like
com.some-company-name.bank-statement/line-item rather than
bank-statement/line-item. Is there already documentation/discussion on this?
Thanks. In that documentation I see
:user/name, but never
::user/name. That's what was confusing me.
What I was thinking about was not using any special feature of Datomic, just having spec kind of namespaces.
Any of those kws are fine to register as names of specs. I would choose one name and be consistent
Yeah you can use specs to validate transaction data payloads without using those features above
Thanks @U050ECB92, am using the long form of namespaces now, but always with
:: in the code, including in pull syntax. Only this long form can be validated by spec - that was my motivation (for others reading this).
As part of doing this I'm creating namespaces (i.e. files) that serve no purpose other than to be used in
:require. Feels like going a bit off the beaten path to be doing this, hence I was looking for some confidence boosting validation 🙂
Is it possible to export a datomic database in datomic cloud? I see how to do it with on prem version, but can't find how with cloud version
iirc a few days ago someone here said it's on of the drawbacks of the cloud version of datomic that there is no way to export it (and then import it into an on-prem datomic setup) can't remember though whether his statement was refuted or not.
btw is it not possible to write a straightforward Clojure script to inspect the schema in the cloud DB and generate the import-export code?