Files
turso/core
Nikita Sivukhin c62b87d9b6 read from database file only if max_frame_read_lock_index is 0 and max_frame > min_frame
- transaction which was started with max_frame = 0 and max_frame_read_lock_index = 0
  can write to the WAL and in this case it needs to read data back from WAL
- without cache spilling its hard to reproduce this issue for the turso-db now,
  but I stumbled into this issue with sync-engine which do weird stuff with the WAL
  which "simulates" cache spilling behaviour to some extent
2025-08-25 11:36:58 +04:00
..
2025-08-15 17:08:53 -04:00
2025-06-23 19:52:13 +01:00
2025-06-30 10:01:03 +03:00
2025-08-21 15:23:59 -03:00
2025-08-21 15:23:59 -03:00
2025-08-15 17:08:53 -04:00
2025-01-28 14:55:38 -05:00
2025-08-21 15:19:16 -03:00
2025-08-21 15:23:59 -03:00
2025-06-23 19:52:13 +01:00
2025-08-12 16:42:38 +05:30
2025-01-28 14:55:38 -05:00
2025-08-21 15:19:16 -03:00
2025-06-23 19:52:13 +01:00
2025-08-21 15:19:16 -03:00
2025-08-21 15:23:59 -03:00
2025-06-30 09:54:13 +03:00
2025-08-21 15:23:59 -03:00