Refs, unique values and :db/index true end up in the :avet. isn't that good enough?

hey @U0CM1QURZ generally that is good enough but I am trying to get the most out of datascript. At the end I went with a solution like you describe, using :db/index true and index-range search with some transducers. The thing is that that was not obvious since the :vaet index doesnt exists, querying for back-references can take 20 times more time than the previous approach

Would it be easy for you to share (e.g repo or gist) what you're doing? That is, what your slow query looks like and how you made it faster using :db/index true and index-range?

I dont have anymore the query anymore since it was a quick comparison but I do have the current code and schema. Here is the code to get the back-references: https://github.com/hiposfer/kamal/blob/datascript/src/hiposfer/kamal/libs/tool.clj#L52. And here is the schema https://github.com/hiposfer/kamal/blob/datascript/src/hiposfer/kamal/services/routing/core.clj#L22

as you can see I am indexing the :node/successors such that I can do index-range on them and get only the values that I am interested in. My guess would be that having a vaet index would avoid that since quick hack since finding those backreferences would be trivial