Alright. I need to make one query, then insert the id of that query as a reference, in a second query right after. What, exactly, do I need to grab from the return of d/transact! that is used as a reference?

(my schema does indicate that in the second query, that field is {:db/type :db.type/ref})

Huh. is it really just {:db/id id}? seems so.

is there any way to.... "resolve" this automatically when querying? like if I have a reference to another item, it could append the whole thing in the result? aka if I do (seq (d/entity @conn [:message/id "275380583893434368"])) I now get this

([:message/type 0]
 [:message/timestamp "2017-01-29T21:44:07.524000+00:00"]
 [:message/channel_id "274707618222833674"]
 [:message/author {:db/id 3}]
 [:message/id "275380583893434368"]
 [:message/mention_everyone false]
 [:message/tts false]
 [:message/nonce "275380580646912000"]
 [:message/pinned false]
 [:message/content "with?"])

([:message/type 0]
  [:message/timestamp "2017-01-29T21:44:07.524000+00:00"]
  [:message/channel_id "274707618222833674"]
  [:message/author ([:user/avatar "a_354e581b44cfc815036869f81c7810c6"]
                     [:user/discriminator "4611"]
                     [:user/id "139412744439988224"]
                     [:user/username "eslachance"])]
  [:message/id "275380583893434368"]
  [:message/mention_everyone false]
  [:message/tts false]
  [:message/nonce "275380580646912000"]
  [:message/pinned false]
  [:message/content "with?"])

(as an arbitrary "Expand all references, event nested ones" if possible)

@eslachance entities are lazy, no need to expand them

when printed, you don’t see that, but if you try to access (:user/id (:message/author (d/entity @conn [:message/id "275380583893434368"]))) you’ll get the id

so entities automatically follow references and any reference attribute is seen as another full entity

but they are realized as you query them, e.g. lazily

What if I need to simply output the whole thing?

(d/touch (d/entity ...))

but that won’t follow nested refs

if you need something like that, you can write your own function that walks all attributes and checks their types

and touches them recursively

Will do. What happens if there's a circular reference though... (yes this will most likely happen)

alternatively, if you know which attributes you want to expand, use Pull API

that’s why DataScript doesn’t do it by default

Alright. I'll need to figure out a way to do this then. I'll go from d/touch and see what I can do. Thank you!

If all goes well within a few months I'll be making some nice tutorial videos for a few things I've learned... most likely Datascript will be part of that because, well, it's awesome 😄

great! Please let me know

I have an app using Datascript that works in dev mode but when I switch advanced compilation I’m getting errors from Datascript, like Lookup ref attribute should be marked as :db/unique: [:state/part :ui] even though I have that attribute set as unique in my schema.

Is it common for users to run into issues like this with advanced compilation, or is that suprising?

it doesn’t look like simply switching to advanced compilation is the problem. I’ll keep looking

I found the culprit! Setting the CLJS compiler option :pseudo-names to true with advanced compilation throws crazy datascript errors. That sounds pretty crazy, but I’ve found it to be true.

Without :pseudo-names

(db/-attrs-by db :db/unique) => #{:db/uuid :state/part}

(db/-attrs-by db :db/unique) => #{{:db.unique :db.unique/identity}}