feat(core): node rows name their parent by local id

Schema 40 adds nodes.parent_lid, backfilled from parent_uid. An upsert
and a new row's stub keep it in step, a folder's new row links the rows
stored before it, and a row merged into a landing folder hands its
children over. A restart places each node under its parent's row as it
is now, so a child whose stored node still names a landed folder's
placeholder lands under the folder's real uid.
This commit is contained in:
nvrl committed 2026-10-04 04:45:47 +02:00
1 parent ae6650f7e0
commit 9b2b9f24c5
5 files changed
+159 -20

No files matched your search

+3 -2
View File
@@ -11,9 +11,10 @@ scratch (user data in `staging/` and `recovery/` is never touched by this).
## [Unreleased]
Schema: **39**. The queue table is rebuilt so an id is never given out twice; queued changes
Schema: **40**. The queue table is rebuilt so an id is never given out twice; queued changes
are kept. Queued changes get a column for the reason Drive refused them, and name their file
and folder by local id as well as by Drive's id.
and folder by local id as well as by Drive's id. Stored files and folders name their parent
folder by local id too.
### Added
- **Sync issues.** A change Drive refuses because the storage is full, access was taken away,