According to the documentation, it does this by preventing callbacks from initiating transactions on the same SpaceBase store? :) :) :) Isn't that a constraint

According to the documentation, it does this by preventing callbacks from initiating transactions on the same SpaceBase store? :) :) :) Isn't that a constraint on the application? :) :) :) I think I'm going to have to look at the demo and see how a shot which triggers an explosion then does the query to perform the push of the surrounding ships. I would expect something like: Ship A: Query(origin+direction+range, callback Shot()) Shot() if Exploding Delete Query(origin, range, callback Boom()) Boom() Update location Except that's not allowed? An AOE which causes cascades of death would be cool to see too. Nifty idea.