Not exactly. There isn’t a way to check a cycle if the transaction wasn’t commited.
And there’s no Rollback. The transaction’s “fine tune/features***” in Dgraph is for internal use only. Dgraph controls what should be rejected, what has conflicts, etc. These things are not exposed to the user.
Anthony, sometimes you lack interpretation. I know exactly what’s available to the end user. I’ve been using Dgraph since 2017. You can assume from this that my phrases are more related to the finer control of a transaction. Which is what Michael is looking for.
There is no Rollback, and there is no checking cycle on the fly(But there is conflict checking on the fly with upsert directive). And it is not possible to query uncommitted transactions. And there’s also no way to introduce logic like “if not do this”. At least for now.