Jussi Saurio a52dbb7842 Handle table ID / rootpages properly for both checkpointed and non-checkpointed tables ...

Table ID is an opaque identifier that is only meaningful to the MV store.
Each checkpointed MVCC table corresponds to a single B-tree on the pager,
which naturally has a root page.

We cannot use root page as the MVCC table ID directly because:
- We assign table IDs during MVCC commit, but
- we commit pages to the pager only during checkpoint
which means the root page is not easily knowable ahead of time.

Hence, we:

- store the mapping between table id and btree rootpage
- sqlite_schema rows will have a negative rootpage column if the
  table has not been checkpointed yet.

2025-09-30 16:53:12 +03:00

..

encryption.rs

clippy fixes

2025-09-27 18:16:51 +05:30

mod.rs

Add regression tests for ALTER TABLE stuff

2025-09-27 09:45:15 +03:00

test_btree.rs

core: Rename IO::run_once() to IO::step()

2025-09-10 14:36:02 +03:00

test_ddl.rs

Add regression tests for ALTER TABLE stuff

2025-09-27 09:45:15 +03:00

test_multi_thread.rs

small fixes

2025-09-17 19:20:42 +04:00

test_read_path.rs

fix clippy

2025-09-30 14:44:48 +04:00

test_transactions.rs

Handle table ID / rootpages properly for both checkpointed and non-checkpointed tables

2025-09-30 16:53:12 +03:00

test_write_path.rs

Encryption support for database header page

2025-09-16 10:04:30 -04:00