you could get a ref to the parent entity and walk its collection(s), or if you want what was just added, you’d use the tempid thing again

Does the tx-report-queue tx-data not contain the fifth datom element (added?). It’s not mentioned in the docs http://docs.datomic.com/clojure/#datomic.api/tx-report-queue

@jonas: The :tx-data entry does contain full E/A/V/T/Op datoms. I will suggest that be clarified in the doc.

@marshall: Thanks

@robert-stuttaford: i want to be able to remove all component IDs in one go … for the moment I have to go through them one by one

I should clarify … I am using a component ref for items in a shopping basket

which seems like a logical way to use that feature

but now I have to do a lot of book-keeping around the elements that are added / updated deleted rather than just sending the map back into datomic and let it handle the book-keeping

does that make sense?

@raymcdermott: seems like it'd be easy enough to write a transaction function for that.

@tcrayford: that sounds tempting … what would I win?

atomicity for one

Yes, makes sense but it still feels like I’m moving boiler plate from one place to another

ah, but the transaction function could be very generic, it doesn't need to be tied to your application at all (which is a pattern I'd generally recommend for transaction functions)

like :db.fn/replaceSubComponents or something

hmmm - yes …. I was hoping that would be in Datomic 😉

but nice idea … I’ll give it a crack

I’m working on an example for the Heroku Datomic thing so it could be good to show that feature

neat

@raymcdermott: I've only written 3 transaction functions in 3 years of using datomic, all of them super generic, which I like a lot.

@tcrayford: I’ll shoot you a link to the code for your comments once it’s done (should be able to finish the Datomic parts over the weekend)

then om.next!

nice 😄