I think I follow the question. Can you give a specific example though, please?

Thank you! So, this example does not do what I naively wanted:

(let [blah "01"]
        (d/q '[:find ?text :where [?m :text ?text][?m :code blah]] @asami-conn))

I’ll be back at my keyboard in 2 minutes…

So… in another world (SQL) it would be something like a prepared statement with parameters and stuff. But here I’m guessing something like appending parameters at the end and they get bound to… things?

No rush!

The thing about SQL is that it's usually based on a string

So you can either modify the string, to include some variable from the local context, or you prepare a query, and then pass the variables along args, similarly to how you might with clojure.core/format

I could try the latter, but it seems redundant when Asami (and Datomic) don't use query strings. We use query structures

The first approach that some people use in the above is to unquote the symbol into place

Avoiding the query call for a moment, you can use:

(let [blah "01"]
  `[:find ?text :where [?m :text ?text][?m :code ~blah]])

Except that also screws with ?m and ?text

Is there an idiomatic way, or am I approaching this all wrong? 🙂

I usually build the query a little more manually. In this case, the query is a vector so you can just conj the last constraint on:

(conj '[:find ?text :where [?m :text ?text]] ['?m :code blah])

but when I'm building a query like that, then I'll usually use the map form instead:

{:find '[?text]
 :where (conj ['[?m :text ?text]] ['?m :code blah])}

(sorry for going back to edit some of these. I had a late night and I only just got up) 🙂

No worries, thanks so much for taking the time. If I want to study this more, why is it that my initial attempt doesn’t work? Anything I can read up on regarding the execution order or something? I’m missing the forest for the trees, I think. 🙂

And thanks for the examples, that helps me understand what you mean by query structures. I’m getting there, slowly 😋

execution order is actually calculated, unless you explicitly ask it not to. That's done by adding, :planner :user to the end of the query arguments

Otherwise, it tries to figure out which are the smallest patterns to resolve, and it sorts the execution order from smallest to largest

(which you should be doing if you're querying Datomic)

This is because Datomic does NOT plan queries. It executes them in the order you request (just like if you used :planner :user at the end of your query parameters)