Anyone else here have a problem when using cast/initialize-redirect :stdout in cider?

works when using the repl from CLI tools, fails within cider 😕

is it possible to create an entity in datomic with no attributes, only refs to it?

Eg I have two entities, 123 and 456, and a :db.cardinality/one :db.type/ref attribute. If I transact [[:db/add 123 :my/ref "foo"] [:db/add 456 :my/ref "foo"]] it fails

What would it be a ref to?

Aren’t you just saying entities 123 and 456 have the string "foo"?

At that point isn’t "foo" just a value instead of an entity?

It'd be a ref to an empty entity. I'm guessing the answer is just "you can't have an empty entity with only incoming references".

Yeah, I mean thats your answer, because it would be kind of like a null entity. I was more questioning what in your domain model would this empty ref represent and, if its a string like you proposed, should you think of "foo" as a static value instead of an entity. I reserve entities for things that change over time but still need a stable id of some sort.

Entities are just a number. You can definitely have an "empty" entity with only 'incoming' refs

Oh! Huh.

Sorry for adding confusion and misinformation then.

Try your example using the map syntax

{:db/id "foo"}
{:db/id 123
 :my/ref "foo"}
{:db/id 456
 :my/ref "foo"}

You could also do list form. Add to your example above: [:db/add "foo" :db/id "foo"]

I believe that last will work. I'm on my phone so I cant check it atm

@matthavener ^^

Note to self: figure out how to run a REPL on my phone :D

user=> (d/with db' [[:db/add 17592186046851 :my/ref "foo"] [:db/id 17592186046852 :my/ref "foo"] [:db/add "foo" :db/id "foo"]])

IllegalArgumentExceptionInfo :db.error/not-a-data-function Unable to resolve data function: :db/id  datomic.error/arg (error.clj:57)

trying map syntax

You need a db/add in the middle list

oh! geez

user=> (d/with db' [[:db/add 17592186046851 :my/ref "foo"] [:db/add 17592186046852 :my/ref "foo"] [:db/add "foo" :db/id "foo"]])

IllegalArgumentExceptionInfo :db.error/not-an-entity Unable to resolve entity: :db/id  datomic.error/arg (error.clj:57)

map version

user=> (d/with db' [{:db/id "foo"} {:db/id 17592186046851 :my/ref "foo"} {:db/id 17592186046852 :my/ref "foo"}])

IllegalArgumentExceptionInfo :db.error/tempid-not-an-entity tempid used only as value in transaction  datomic.error/arg (error.clj:57)

fwiw this is not a huge issue, we can add a token attribute onto "foo". I just thought it was weird 🙂

It should work. I'll try to look into it this weekend

Cloud or onprem? And version?

om-prem, 0.9.5561

Ok

no this is correct, you can't use a tempid without using it as an :e in some assertion in the tx

consider reversing the attribute?

Why does datomic.client.api/transact not throw an error when called like this?

(d/transact conn [{:db/id         bob-id
                   :user/name "bob"}])

what is bob-id?

I'm guessing it resolves to some value that would be legal there?

A :db/id. Doesn't matter for this. transact needs to provide feedback on the incorrect call.

what is incorrect?

Should be:

(d/transact conn {:tx-data [{:db/id     bob-id
                             :user/name "bob"}]})

oh cloud api

sorry

Yes. And I'm so used to the peer API I always forget to call it correctly.

forever confused that they use the same prefix by convention

yes that is terrible

it should error

map? predicate at least

if you give a non-sequential to the peer d/transact it errors

cloud should do likewise if it gets non-map

I agree 100%. Right now the transaction succeeds, only transacting :db/txInstant.