Clojurians Log v2
datomic
@val_waeselynck Hi Valentin, I just finished reading your very interresting post "Using Datomic in your app: a practical guide" https://vvvvalvalval.github.io/posts/2016-07-24-datomic-web-app-a-practical-guide.html I would like to know, 4 years later, what would be the points that have changed the most?
@rob703 consider putting your python code to separate environment and interact via lambdas
I did consider this yesterday evening, it just looses the charm of being able to work with the code through clojure. Setting up a completely separate python environment and accessing it via remote calls just isn't the same as simply using it directly. But yes, if all things fail that will be our workaround. It won't be too bad, but I still hope someone comes up with another solution
Is it just me, or does everyone think of John McCarthy’s http://www-formal.stanford.edu/jmc/elephant/elephant.html when they contemplate Datomic?
@admin055 nothing much has changed really. Datofu has been added to automate some common tasks such as schema declaration and migrations: https://github.com/vvvvalvalval/datofu Some frameworks now make Datomic a bit more battery-included, such as Fulcro or Hodur. I've used neither.
1👍
It may be just you @hiskennyness -- I'd never heard of Elephant 2000 until you mentioned it. Looking at the syntax, Elephant reminds me more of Prolog than Datalog but I guess that's where the connection comes in?
“It may be just you”. It happens, @seancorfield.The connection I see is “An elephant never forgets!“, ie the possibility of painlessly referring to the past. Fun note: I actually remembered E2K as a DB proposal!
Ah, yes, gotcha!
A more substantial http://www-formal.stanford.edu/jmc/elephant/node3.html#SECTION00030000000000000000.
New Datomic Cloud Release ^
@val_waeselynck Perfect, thanks. This is clearly one of the strength of Clojure. (y) Another thanks for the Datofu link, I was just telling myself that the schema declaration had perhaps evolved.
From my AWS EBS application, I’m failing to make a simple datomic.client.api/client call to a Datomic Cloud Solo topology.
Details here. Am I missing something?
https://stackoverflow.com/questions/64037250/datomic-client-api-client-failing-to-reach-a-datomic-cloud-solo-topology
Ah clever, that’s a great use of queries as data. I can see how you could have a toolbox of interceptors for common things like [?e :user/id ?user-id-from-cookie]
Ok, got past this. Now getting the error.
{:cognitect.anomalies/category :cognitect.anomalies/forbidden, :cognitect.anomalies/message "Forbidden to read keyfile at s3://<path>/db/<my-app>/read/.keys. Make sure that your endpoint is correct, and that your ambient AWS credentials allow you to GetObject on the keyfile."}Thinking more, you could even build :accessible/to into the schema, and assert it onto entities to authorize access by the referenced entity (ie a user). That might be generalized into an interceptor more gracefully.