It can be done for filtering, otherwise it is really tricky (I am not even
sure it can be done to be honest).
On Sun, Sep 9, 2018 at 2:11 AM, Dmitry Lazurkin wrote:
> Hello.
>
> Does it make sense to implement != restriction in select-where clause?
> Is it possible?
>
> Thank you.
>
> PS. I
Hi,
You can only use IF = or IF != on insert, update or delete statements, it does
not work on select. When using it, it will create a LWT transaction and you'll
need full PK in the where condition, you can apply the IF on values of the row.
For example:
update table set type =
Yes, but I need for select ;-)
пн, 10 сент. 2018 г., 11:03 Jacques-Henri Berthemet <
jacques-henri.berthe...@genesys.com>:
> Hi,
>
> You can only use IF = or IF != on insert, update or delete statements, it
> does not work on select. When using it, it will create a LWT transaction
> and you'll
Thank you. Yes, I known, it's working only for ALLOW FILTERING. Ok, I
understand, it's possible.
пн, 10 сент. 2018 г., 11:24 Benjamin Lerer :
> It can be done for filtering, otherwise it is really tricky (I am not even
> sure it can be done to be honest).
>
>
>
> On Sun, Sep 9, 2018 at 2:11 AM,
I like Jon's idea, plenty of food for thought in terms of a 4.0
retrospective + what's on the future.
On Wed, Sep 5, 2018 at 1:18 PM sankalp kohli wrote:
> Another thing to discuss will be how to improve testing further from the
> learning of finding bugs in C* 4.0.
>
> On Wed, Sep 5, 2018 at
