Avi Kivity 390a0ca47b types: allow lists with NULL ...

Allow transient lists that contain NULL throughout the
evaluation machinery. This makes is possible to evalute things
like `IF col IN (1, 2, NULL)` without hacks, once LWT conditions
are converted to expressions.

A few tests are relaxed to accommodate the new behavior:
 - cql_query_test's test_null_and_unset_in_collections is relaxed
   to allow `WHERE col IN ?`, with the variable bound to a list
   containing NULL; now it's explicitly allowed
 - expr_test's evaluate_bind_variable_validates_no_null_in_list was
   checking generic lists for NULLs, and was similary relaxed (and
   renamed)
 - expr_Test's evaluate_bind_variable_validates_null_in_lists_recursively
   was similarly relaxed to allow NULLs.

2023-01-18 10:38:24 +02:00

..

collection.hh

test: relax NULL check test predicate

2023-01-18 10:38:24 +02:00

list.hh

treewide: drop cql_serialization_format

2023-01-03 19:54:13 +02:00

listlike_partial_deserializing_iterator.hh

types: allow lists with NULL

2023-01-18 10:38:24 +02:00

map.hh

treewide: drop cql_serialization_format

2023-01-03 19:54:13 +02:00

set.hh

test: relax NULL check test predicate

2023-01-18 10:38:24 +02:00

tuple.hh

types/tuple: Use std::begin() instead of .begin() in tuple_type_impl::build_value_fragmented

2022-08-14 10:29:52 +03:00

user.hh

implement keyspace_element interface

2022-12-10 12:34:09 +01:00