Jussi Saurio 4c76191fec fix/sim: fix incorrect implementation of compound select generation ...

Problem:

sim was generating compound selects like this:

- pick a random `table`
- create a random single SELECT
- create `n` random compound SELECTs (UNION ALL etc)

assign a WHERE clause that always has a condition based on `table`

This can result in e.g.

```
SELECT a FROM foo WHERE bar.x = 'baz'
```

Solution:

Don't base the WHERE clause on a table that might not be referenced
in the query.

Again, the only reason this wasn't caught before was because `FaultyQuery`
and `FsyncNoWait` are the only paths where this is actually tested with an
assertion, and those are both disabled

2025-08-15 10:48:42 +03:00

..

predicate

parser: Distinguish quoted identifiers and unify Id into Name enum

2025-07-24 14:40:19 +05:30

expr.rs

parser: Distinguish quoted identifiers and unify Id into Name enum

2025-07-24 14:40:19 +05:30

mod.rs

add random_expr for SELECT <expr>;

2025-07-14 18:48:02 -04:00

plan.rs

sim: provide additional context in assertion failures

2025-07-16 12:05:30 +03:00

property.rs

sim: add Property::ReadYourUpdatesBack

2025-08-14 19:04:27 +03:00

query.rs

fix/sim: fix incorrect implementation of compound select generation

2025-08-15 10:48:42 +03:00

table.rs

make the large table smaller

2025-07-15 09:56:27 -04:00