Repository navigation
v2.0.2
Fix: the 1.x → 2.0 move into an org could stop on installs with consolidated observations
On 1.3+ installs, the one-time move into the org database could stop with memory: N in the old database, N-1 in the new. Nothing was lost (the move verifies before it finishes), but the app stayed offline.
Cause: observations from 1.3+ carry obs_subject, a field 2.0's stricter schema no longer has. SurrealDB 3 refuses such a row, and the copy skipped it.
Fix: rows are copied without fields the 2.0 tables don't define, and the move logs which fields it left out.
If you hit this on 2.0.0 or 2.0.1: update to 2.0.2 (or run docker compose up -d after updating). The move resumes and completes; your old data is untouched.