Hey.. Now that I am more familiar with parser and query syntax, I am building an app with Datomic on the back-end. Concerning mutations. Is there any link / interop between om.next tempid and Datomic tempid? I receive :result {:tempids …} from mutation, what should I do with it ( in terms of optimistic updates) ? Or should I just re-read my remote keys?

@arohner oh so your problem is with links?

(looking at your example now)

It is now 🙂

Links look closest to what I want to achieve, and would result in pretty clean code, if links triggered sends

I'll have to look at the issue you opened, but I think I know what's wrong with the example above

I think the path we were going down yesterday was messy and got too involved in Om internals

@arohner so one thing though is that links aren't really supposed to be sent to the server

which is why adding :foo/bar to the top-level query effectively works for the case of your issue

so if child queries for [[:foo/bar _]], I agree [[:foo/bar_]] shouldn’t be sent

but I would expect that to result in a client-side read for [:foo/bar]

and if client-side :foo/bar returns {:remote true}, that would be a send for :foo/bar

well it doesn't, really

Links are supposed to be used with db->tree

db->tree will understand that a link refers to a top level prop in the app state when it sees one

right, so there’s no convenient way currently to combine db->tree with sends

I got the recursive read stuff to work eventually yesterday, but it seemed to get into the internals too much, and without links, it wouldn’t render properly

@arohner they're meant for different purposes. if you want to modify / extract stuff from the query you send to the remote, you can manipulate the AST

but then the recursive-read stuff would need to be extended to support links