Hmm.. Maybe my setup is at fault, but even conj'ing $ to the arguments list didn't do it.

Oh!

Pattern goes Last?

Wow.

Thank you very much @favila

Man. Mind blown.

So, I’m I’d like to monitor the tx-report-queue for changes and react to them, but I’m noticing the attribute keywords are not present. It appears they are being represented by the entity ids that were transacted when creating the schema. Is that correct? (d/transact conn* [{:db/id (tempid), :test/attr “Abcde”}])

{:db-before datomic.db.Db,
 @234dd5c2 :db-after,
 datomic.db.Db @d16ab2c7,
 :tx-data [#datom[13194139534314 50 #inst"2017-01-14T19:15:46.413-00:00" 13194139534314 true]
           #datom[277076930200555 64 "Abcde" 13194139534314 true]],
 :tempids {-9223090561879065153 277076930200555}}

In the above example it appears that :test/attr is being represented as 64

@seantempesta Attributes are entities as well!

Those are the entity ids for each attribute.

Is there an easy way to look them up? I was hoping calling (.a datom) would do it, but it just returns 64.

You can access the corresponding keyword for an attribute id via d/ident.

rad! thanks!

np!

Silly question here -- I'm trying to cut over from Datomic Pro to Datomic Free on a project, to let other developers spin up with less overhead, I'm having some trouble documenting how to get services started up -- with datomic-free-0.9.5544, bin/run -m datomic.peer-server fails saying it can't find datomic/peer_server__init.class or datomic/peer_server.clj, and indeed, I don't see them around in the distributed jars -- what am I missing?

...hmm; datomic-transactor-pro-0.9.5544.jar contains AOT'd datomic/peer_server, but datomic-transactor-free-0.9.5544.jar doesn't.

...it's not that new of a release, so I can't see this being an undetected bug...

...ahh.

didn't grok that the peer is what the client connects to. Now this makes sense. 🙂

@tcarls did you figure out your issue?

Yup.