Fork me on GitHub
James Vickers01:02:18

Does anyone have experience writing a GraphQL resolver that queries from Datomic (pull)? Is that pretty straightforward because of how pull works?


Depends on your authorization model and of the need for derived fields. I have set up a query server with similar semantics to graphql, and Datomic pull fell short for these reasons.


Custom caching logic and complementary data sources (e.g blob stores) can be other reasons why pull might be insufficient.


Oh and I forgot parameterized fields, of which pull has none either


So pull might be helpful locally, but I wouldn't count on it to just execute a whole GraphQL query.


If you're on a Peer and using Lacinia, I think expressing your resolvers in terms of the Entity API and occasionally Datalog is much less limiting.


Yeah, the entity API + lacinia work beautifully together


I just noticed that the client api find spec only has find-rel and is missing find-coll find-scalar and find-tuple. Are those coming later or were they intentionally omitted?


@adamfrey the client API has always used only find-rel if you’re interested in other options, I’d suggest you add a feature to our feature suggestion portal