I don't interop datascript/datomic, but I use d/tempid on both

d/tempid will return decreasing negative numbers in cljs, which won’t fly when submitted to datomic

Do you want to generete tempids om clients, serialize/send to server, transact and get back? Not sure but #om tempid's may do that.

(may help you to do that.)

something like that. Don’t use om btw. The client generates transaction data which gets send to the server, which then replies with the created datoms. My client now kinda produces string temp-ids to be able to make that happen, would love to already transact those in datascript too to get some optimistic updates, and replace those when the server reply gets back.

There are hacks though, like using string negative numbers and looking for them, parseInt’ing them on the client for datascript, and doing some matching etc.. when the tx report comes back. But it’s a bit of a hassle and error prone, was wondering how the rest of the community handles this.

I think that you can tweak the print-method

No, datascript tempid is a primitive

did you know #specter? you can (transform [(walker :db/id) :db/id (pred neg-int?)] d/tempid edn) on the server

I know specter. Could be useful here indeed, thanks 🙂

Actually, d/tempid will return a new one and I lose all references to the original tempid integer (ie: :tempids in the report contains other ones than the client sent out, which makes it hard to reconcile it when the response comes back. Not impossible, but just a lot of hassle. I’m curious to how other people in the community handle this.

(= (d/tempid :db.part/user -65) (d/tempid :db.part/user -65)) ; => true

or you can just stringify the negint from datascript

what I meant was:

(d/transact conn [[:db/add (d/tempid :db.part/user -1) :some/attr some-val]])
; => {... :tempids {-9223350046622220289 17592186048880} }