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?

https://docs.datomic.com/cloud/schema/schema-reference.html#attribute-predicates https://docs.datomic.com/cloud/schema/schema-reference.html#entity-specs @cjmurphy

(Yes it is a good idea)

Thanks. In that documentation I see :user/name, but never :i.am.a.spec.user/name, or ::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

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

0.9.34 ion is broken for (cast/event ...), had to downgrade to 0.9.28 ion