I imagine that conditions would be evaluated against the state prior to the
execution of statement against which it is being evaluated, but after the prior
statements. I think that should be OK to reason about.
i.e. we might have a contrived example like:
BEGIN TRANSACTION
UPDATE tbl SET a = 1
> It affects not just RETURNING but also conditions that are evaluated against
> the row, and if we in future permit using the values from one select in a
> function call / write to another table (which I imagine we will).
I hadn’t thought about that... using intermediate or even post update val
I’ve opened a PR: https://github.com/apache/cassandra-website/pull/137
Not sure what our commit norms are for the website, but I’m assuming we would
normally expect a +1 from somebody else.
From: Dinesh Joshi
Date: Saturday, 4 June 2022 at 19:59
To: dev@cassandra.apache.org
Subject: Re: [DISCU
