Differences between :db/ident and :id

[bmaddy]

Looking at the documentation on Identity Values (https://github.com/threatgrid/asami/wiki/4.-Transactions#identity-values) makes me think :db/ident and :id would operate the same but only :id would show up in entity maps. However, I'm seeing something different when I transact things. It's most easily seen in build-triples:

(->> (asami.entities/build-triples
      asami.index/empty-graph
      [{:id "1111"}
       {:db/ident "2222"}
       {:id "1111"}
       {:db/ident "2222"}])
      first
      (filter (fn [[_ attr]] (contains? #{:id :db/ident} attr))))

;; returns
([:tg/node-32897 :id "1111"]
 [:tg/node-32897 :db/ident :tg/node-32897]
 [:tg/node-32898 :db/ident "2222"]
 [:tg/node-32899 :id "1111"]
 [:tg/node-32899 :db/ident :tg/node-32899])

I would expect that to return

([:tg/node-32897 :id "1111"]
 [:tg/node-32897 :db/ident :tg/node-32897]
 [:tg/node-32898 :db/ident "2222"])

Is this the expected behavior?

I'm on Asami version "2.1.3".

For a little context, I came across this because I'm importing some json from an endpoint I don't have control over. Conveniently, it has uuids on an "id" attribute, but it does duplicate the data of some entities when nested. I was surprised to see that generate multiple copies even when they had an "id" uuid. I can work around it easily enough by parsing the json myself and adding a :db/ident whenever I see an :id, but was mostly wondering if :id and :db/ident were supposed to have differences like this.

Also, I've been having a lot of fun with Asami over the past few weeks--thanks for making it!