Files
turso/core
Pekka Enberg 20d3399c71 Merge 'implement is and is not where constraints' from Glauber Costa
The main difference between = and != is how null values are handled.
SQLite passes a flag "NULLEQ" to Eq and Ne to disambiguate that.
In the presence of that flag, NULL = NULL.
Some prep work is done to make sure we can pass a flag instead of a
boolean to Eq and Ne. I looked into the bitflags crate but got a bit
scared with the list of dependencies.
Warning:
The following query produces a different result for Limbo:
```
select * from demo where value is null or id == 2;
```
I strongly suspect the issue is with the OR implementation, though. The
bytecode generated is quite different.

Reviewed-by: Jussi Saurio <jussi.saurio@gmail.com>

Closes #847
2025-02-01 17:24:11 +02:00
..
2025-01-30 03:44:33 +02:00
2025-01-28 14:55:38 -05:00
2025-01-31 06:44:56 -05:00
2025-01-29 22:37:04 +02:00
2025-01-28 14:55:38 -05:00
2025-01-11 17:19:25 +02:00
2024-12-24 18:04:30 +01:00
2025-01-26 16:27:19 +02:00