Jan Ciolek aa604bd935 cql3: preserve binary_operator.order in search_and_replace ...

There was a bug in `expr::search_and_replace`.
It doesn't preserve the `order` field of binary_operator.

`order` field is used to mark relations created
using the SCYLLA_CLUSTERING_BOUND.
It is a CQL feature used for internal queries inside Scylla.
It means that we should handle the restriction as a raw
clustering bound, not as an expression in the CQL language.

Losing the SCYLLA_CLUSTERING_BOUND marker could cause issues,
the database could end up selecting the wrong clustering ranges.

Fixes: #13055

Signed-off-by: Jan Ciolek <jan.ciolek@scylladb.com>

Closes #13056

2023-03-06 16:28:06 +02:00

..

expression.cc

cql3: preserve binary_operator.order in search_and_replace

2023-03-06 16:28:06 +02:00

expression.hh

cql3: expr: introduce adjust_for_collection_as_maps()

2023-02-12 17:25:46 +02:00

prepare_expr.cc

treewide: do not define/capture unused variables

2023-02-15 22:57:18 +02:00

restrictions.cc

cql3: expr: move check for ordering on duration types from restrictions to prepare

2023-02-12 17:17:01 +02:00

restrictions.hh

cql3: expr: Remove convert_to_restriction

2022-07-20 09:10:31 +02:00

unset.hh

cql3, transport, tests: remove "unset" from value type system

2023-01-16 21:10:56 +02:00