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 think that for it to be intuitive we need it to make sense sequentially,
whi
That's a good question. I'd lean towards returning the final state of things,
although I could understand expecting to see intermediate state. Regarding
range tombstones, we could require them to precede any updates like selects,
but there's still the question of how to handle multiple updates t
> if multiple updates end up touching the same cell, I’d expect the last one to
> win
Hmm, yes I suppose range tombstones are a plausible and reasonable thing to mix
with inserts over the same key range.
What’s your present thinking about the idea of handling returning the values as
of a given
Hi all,
Thanks for all the input and questions so far. Glad people are excited about
this!
I didn’t have any free time to respond this weekend, although it looks like
Benedict has responded to most of the questions so far, so if I don’t respond
to a question you asked here, you can interpret t
FYI - as there are a few details that need confirming on the World Party,
I've pushed the publication of this post back to Thursday, 9 June. Thanks!
On Tue, May 31, 2022 at 10:07 PM Chris Thornett wrote:
> We have a 72-hr community review for the first blog announcing this year's
> Cassandra Wor
On Mon, Jun 6, 2022 at 5:28 PM bened...@apache.org
wrote:
> > One way to make it obvious is to require the user to explicitly type
> the SELECTs and then to require that all SELECTs appear before
> UPDATE/INSERT/DELETE.
>
>
>
> Yes, I agree that SELECT statements should be required to go first.
>
> One way to make it obvious is to require the user to explicitly type the
> SELECTs and then to require that all SELECTs appear before
> UPDATE/INSERT/DELETE.
Yes, I agree that SELECT statements should be required to go first.
However, I think this is sufficient and we can retain the shorter f
Thank you Blake and team!
Just some personal reactions and thoughts...
First instinct is to support the shorter format where UPDATE ... AS car is
also its own implicit select.
However, a subtle thing to note is that a reasonable user might expect that
in a sequence of multiple UPDATEs, each of
Yes, sorry, I'd locked it down. I've added you as an editor if you need to
make any more changes.
On Wed, Jun 1, 2022 at 4:22 AM Erick Ramirez
wrote:
> Chris, I just realised that no one had access to the doc.
>>
>
> Or maybe you've removed access since the review period has passed. My bad.
> 🙂
