that worked in earlier version, I changed the latter clause to [(identity :some-value) ?type] and it works now

related note, is there anything users could do to help progress that bug ? fixing it might be too difficult for someone not versed in the internals

but it is quite cumbersome to workaround, needing to split complicated queries to multiple queries... especially when dynamically generating where clauses

^ by the above I mean the gh issue 1533

(noted - will circle back to this in the next day or so)

hey @U11SJ6Q0K 👋 thanks for the report. I'm afraid I can't repro this though - I'm doing the following: tx: [[::xt/put {:xt/id :foo, :type :some-value}]] q:

(t/is (= #{[:foo]}
         (xt/q (xt/db *api*)
               '{:find [?e]
                 :where [[?e :xt/id]
                         [(get-attr ?e :type) [?type]]
                         [(= ?type :some-value)]]})))

is that what you're seeing?

I'll try

that particular example works... I'll double check what is the difference in my actual query

might be related to or perhaps, here is a failing example

(xt/submit-tx node [[::xt/put {:xt/id :foo, :type :some-value :term "search by this"}]])

(xt/q (xt/db node)
      '{:find [?e]
        :where [[(get-attr ?e :type) [?type]]
                [(= ?type :some-value)]

                (or [(text-search :term term) [[?e]]]
                    [(text-search :term other) [[?e]]])]
        :in [term other]}
      "search" "this")

seems to happen with regular triple clauses in or as well, not related to text-search

simpler example that fails as well

(xt/q (xt/db node)
      '{:find [?e]
        :where [[(get-attr ?e :type) [?type]]
                [(= ?type :some-value)]

                (or [?e :type :some-value]
                    [?e :type :other])]})

great, cheers 🙂

yeah, this does seem related to some refactoring that happened as part of 1.21.0. will take a look

suspicious 😅 thanks for joining!

Thanks for the warm session learnt some really cool things which I can explore!