Not sure how different datalog queries in xtdb are from datomic, but this works in datomic at least:

(d/q '[:find ?e ?a ?v
         :in $ [?a ...]
         :where
         [?e ?a ?v]]
       app-db
       [:key1 :key2])

Yeah… I get this when I run that code

Your original query has too much nesting, I think

Also, the brackets in your :find clause will give you only a single result.

(Again, in Datomic 😅 )

Hmm… no. The datalog dialect is different. The query itself is correct

ok, then I'm sorry for the noise

No worries 🙂

Mucho loves @U9MKYDN4Q 😛

hehe

If I'm not mistaken, you cannot have the ?k variable in XT's Datalog. It needs to be specified ahead of time.

You could do an or query against the :key*s

What would that look like?

(xt/q (xt/db node)
  '{:find [?e ?v]
    :where [(or [?e :key1 ?v]
                [?e :key2 ?v]
                [?e :key3 ?v])]})

OK. So that still assumes you know the key ahead of time?

Yep. But your original example also does. (If I'm not mistaken, your query and my query are equivalent.)

It is one of the shortcomings of XT's Datalog. I've always been able to get around it, though.

Right. I did say in the next comment underneath the parent of this thread I don’t know the value of ?k ahead of time 🙂

It was just an example

I have another implementation that gets what I want. Just not as elegant

For completeness, if the key is truly unknown ahead of time, there's a way through the attribute-statshttps://juxt-oss.zulipchat.com/#narrow/stream/194466-xtdb-users/topic/reverse.20references.3F/near/255741555.

Hmmm… I could probably generate a query then with an or clause

this was a hack, never tested thoroughly...but might be useful if you really want something dynamic https://gist.github.com/refset/93135adcbf41fccab9b641638ab10997