I suspect this is not supported in FluxGraph because it is prohibitively difficult. In principle, Datomic can support the Blueprints way of allowing uncommitted changes to be queried within a TX by combining the existing database with a set of transforming statements using the with function. With some changes to the way element IDs are handled to ensure that temp IDs are resolved to actual ones after a commit, this seems to let a few of the tests pass.
However, this thread seems to confirm there are difficulties here when adding and removing an element within a single transaction.
I suspect this is not supported in FluxGraph because it is prohibitively difficult. In principle, Datomic can support the Blueprints way of allowing uncommitted changes to be queried within a TX by combining the existing database with a set of transforming statements using the with function. With some changes to the way element IDs are handled to ensure that temp IDs are resolved to actual ones after a commit, this seems to let a few of the tests pass.
However, this thread seems to confirm there are difficulties here when adding and removing an element within a single transaction.