Logflare / logflare / 043ea026b31ccfcd0fb3d12ae9223b90cd6a9276-PR-2676

69%

main: 71%

Pull #2676

github

fix: lql negations should consider null as not matching

When filtering for `-metadata.project:"asd"`, logs without
the `metadata.project` key wouldn't show up. This happened due
to how LQL negations got translated to SQL:

Before: `-m.project:"asd"` would become:
```sql
WHERE NOT (f1.project = 'asd')
```

If `f1.project` IS NULL, the expression returns NULL, which
filters it out of the result set.

Now we translate it to:
```sql
WHERE ((f1.project IS NULL) OR NOT (f1.project = 'asd'))
```

This properly returns logs where m.project is null.

3 of 3 new or added lines in 1 file covered. (100.0%)

7210 of 10393 relevant lines covered (69.37%)

4106.45 hits per line