@mrjn I have few questions about the transactions.
Is there a way, or will there be one, to query transactions without being committed? I mean, if we somehow “lose” the information because of a technical problem, we lose “start_ts” and so on. How to proceed? how to “list” the uncommitted transactions? - if applies*.
Will there be a “timer” commit limit? Is there a way to define a limit ourselves? Could we define “rules” for commitment to happen automatically? - if applies*.
And if we need to revert the transaction without needing a new mutation. There could be something like “uncommit” / “revert” / “checkout” / “Undo”/“rollback”? and the commitment “rules” could be applied too for this question.
And are there more future plans for something new* with transactions?
Of course all these things from my questions should be a Queries / mutations affected by admin. Maybe only “reverted” commitment transactions should be informed to clients.
ps. Maybe my questions are silly. But they seem to be pertinent to me. Because I see them related to ACID logic idea.
Best Regards.