DarkRoom

The merge inserted every incoming collection with `parent_id = NULL` and
never set it on update, so the hierarchy flattened on each round trip: a
collection nested on one device came back from the server at the top
level. `r.parent_id` was selected and then not read.

The id could not be copied — row ids are local, and the remote's integer
names a different collection here, or none. So carry the parent's uuid
and resolve it locally, in a second pass: rows arrive in whatever order
the query returns, and a child can precede its parent.

Guard the resolution against cycles. Each tree is acyclic alone, but the
union need not be — we may hold A above B while the remote holds B above
A — and closing that loop would make every tree walk spin.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-17 21:55:09 +02:00

examples

Let a folder on this machine be scanned into the catalog

2026-08-17 08:59:17 +02:00

src

Let a sub-collection stay under its parent through a sync

2026-08-17 21:55:09 +02:00

Cargo.toml

Let a folder on this machine be scanned into the catalog

2026-08-17 08:59:17 +02:00