## Changed in 0.9.5651
* Enhancement: Peer server allows arbitrary code in queries.
* Enhancement: Better error messages from peer server.

sounds like something that’s not a component maybe 🙂

it definitely is, in just case though we accidentally created a duplicate of the parent (unique value got changed in source data) and now have two streams of components that I need to merge…

You can definitely move it. Retract from its existing parent and assert on the new one in the same tx

Then it dawn on me that I could possibly transact [{:db/id component-id :parent/_id new-parent-id …}] and voila… Except not

[[:db/retract old-parent attr component][:db/add new-parent attr component]]

You cannot retract anything with the transaction map syntax

the map syntax is sugar for :db/add only

yep, got that… in your example, what would the value of component be?

the whole component entity as a map, or just the entity id

the component entity

only the id

hmm, thanks, let me have a look quick

All transactions expand to a list of primitive :db/add and :db/retract operations. Map syntax is sugar for a bunch of db/adds, and transaction functions must return something that eventually bottoms out with db/add or db/retract.

db/add and retract don't take maps as arguments

thanks, confirmed your suggestion with retract/add in the same transaction has the desired effect!

it just never occurred to me to tackle it that way around

You could make a transactor fn to perform an atomic swap if you often need to query for the old parent before transacting