Is there a idiomatic way for generating tmpids? gensym or randomUUID come to mind - whatever I realized for my use case I already have a unique string at hand

[?order :shop/line-items ??]

;; How do I get the order back when I have a line item?

;; I want to do what it says here
;; 

;; like this but I have cardinality/many

[?release :release/artists ?artist]

@benjamin.schwerdtner

(def order-from-line-item
 '[:find ?order
   :in $ ?line-item
   :where
   [?order :shop/line-items ?line-item]])

(def the-db (d/db the-conn))
(def line-item-id "abc123")
(d/q {:query order-from-line-item :args [the-db line-item-id]})

What is the most succinct way to assert a unique entity? I thought I can do something like

(d/transact
   conn
   {:tx-data
    [{:db/id [:unique/id "bestid5"]}]})

(d/pull
   (d/db conn)
   '[*]
   [:unique/id "bestid5"])
=> #:db{:id nil}

You're close, (d/transact conn {:tx-data [{:unique/id "bestid5"}]})

Now I'm trying this to assert and reference the unique in the same tx

(d/transact
 conn
 {:tx-data
  [{:airstats.pipeline/id "bestid4"}    ;a unqiue
   {:airstats.job/pipeline              ;ref to unique
    [:airstats.pipeline/id "bestid4"]}
   {:airstats.job/pipeline              ;I'll have multiple of those
    [:airstats.pipeline/id "bestid4"]}]})

"Unable to resolve entity: [:airstats.pipeline/id \"bestid4\"] in datom [-9223301668109598094 :airstats.job/pipeline [:airstats.pipeline/id \"bestid4\"]]",

Yep, you need a tempid

(d/transact
 conn
 {:tx-data
  [{:airstats.pipeline/id "bestid4"
    :db/id "tempid-for-bestid4"}    ;a unqiue
   {:airstats.job/pipeline              ;ref to unique
    "tempid-for-bestid4"}
   {:airstats.pipeline/id "bestid5"
    :db/id "tempid-for-bestid5"}
   {:airstats.job/pipeline              ;I'll have multiple of those
    "tempid-for-bestid5"}]})

:airstats.job/pipeline is supposed to be a ref to an entity with :airstats.pipeline/id and multiple jobs can ref 1 pipeline. Thanks will check. Maybe I should rethink the schema and have jobs as a reference component on the pipeline entity

My only generic advice for you is to try and avoid thinking in rectangles if you can. Datomic doesn't operate in structs of entities. Instead, like Clojure, it operates as sets of attributes.

(TBC, I'm not saying what you were asking about was necessarily bad or particularly rectangular)

haha I'll meditate on that!

Could duplicate :where clauses impact query performance in any way?