Files
turso/core/translate
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
..
2025-09-25 17:14:54 -04:00
2025-09-26 12:17:34 -04:00
2025-09-29 16:30:07 +04:00
2025-09-26 13:01:49 +04:00
2025-09-30 15:28:50 +04:00
2025-06-11 18:38:56 +02:00
2025-09-26 13:01:49 +04:00
2025-09-13 11:12:44 +02:00