Glauber Costa 3dc1dca5a8 use 128-bit hashes for the zset_id ...

We have used i64 before because that is the size of an integer in
SQLite. However, I believe that for large enough databases, the chances
of collision here are just too high. The effect of a collision is the
database silently returning incorrect data in the materialized view.

So now that everything else is working, we should move to i128.

2025-09-25 22:52:08 -03:00

..

aggregate_operator.rs

use 128-bit hashes for the zset_id

2025-09-25 22:52:08 -03:00

compiler.rs

core: Wrap Connection::query_only with AtomicBool

2025-09-24 19:23:13 +03:00

cursor.rs

core: Wrap Connection::schema in RwLock

2025-09-23 10:31:20 +03:00

dbsp.rs

use 128-bit hashes for the zset_id

2025-09-25 22:52:08 -03:00

expr_compiler.rs

Merge 'Introduce instruction VTABLE' from Lâm Hoàng Phúc

2025-09-18 09:18:48 +03:00

filter_operator.rs

support column comparisons in the filter operator

2025-09-19 03:59:28 -05:00

input_operator.rs

move the input operator to its own file.

2025-09-19 03:57:11 -05:00

join_operator.rs

use 128-bit hashes for the zset_id

2025-09-25 22:52:08 -03:00

merge_operator.rs

use 128-bit hashes for the zset_id

2025-09-25 22:52:08 -03:00

mod.rs

Implement the DBSP merge operator

2025-09-21 21:00:27 -03:00

operator.rs

use 128-bit hashes for the zset_id

2025-09-25 22:52:08 -03:00

persistence.rs

Replace custom serialization with a saner version

2025-09-25 22:52:08 -03:00

project_operator.rs

core: Wrap Connection::query_only with AtomicBool

2025-09-24 19:23:13 +03:00

view.rs

make sure that complex select statements are captured by MV populate

2025-09-21 21:00:27 -03:00