Tatu Tarvainen

Still seems to be a problem with 1.21.0-beta1. I have a query that takes ~2.5ms with the `get-attr` workaround and ~1200ms a regular triple clause.

Adding new attributes to any `:db/ident` entities seem to fail ```clojure (defn dh-update-exception [] (let [uri "datahike:mem://test"] (datahike.api/create-database uri) (let [c (datahike.api/connect uri)] ;; Add two enum values (datahike.api/transact c...

Yes, the higher level automation API is a good place for utilities. I'll happily accept PR's, when adding utilities please follow the same style as the already existing ones. And...

Thanks for the bug report. I'll add a test-case for that so that it gets fixed in the next version. Unfortunately, for now you may need to do 2 queries.

We need to support them in a similar fashion for both regular columns and user defined type parsing. Perhaps we need to query regular range column as text and use...

Many cases could be made to work with a clever WHERE clause, but I agree that specifying a join condition would be handy. From the top of my head, I...

I haven't had the need for this, but it is a good feature to implement. You should be able to do this with minor changes to the catalog queries. PR...

Thinking of reseving vector keys for references to related entities in where clause

```clojure (xt/submit-tx node [[::xt/put {:xt/id "missing-test1" :some-missing/attribute "NEW VALUE"}]]) ``` After submitting a new tx with a simple put that has one of the missing attributes, it appears in attribute-stats,...

What are the implications of this? Is it safe to run 1.22.0? Does the stats missing have any negative effects?