Skip to content

Session

Jump to bottom
github-actions[bot] edited this page Oct 12, 2026 · 3 revisions

tags: [domain-model] store: sessions legacyStore: results keyPath: "id" db: wodwiki-db (v29)

Session

[!info] Implementation Note Renamed from WorkoutResult (table results → sessions, DB v20) and flattened in V21: the statement stream no longer lives on the row. Every statement is an EventRecord. The sparse cutover (DB v29) replaced segment pins with the immutable block revision pin.

Current State (Implemented in Code)

  • Store: sessions (legacy results copied on V20, flattened on V21)
  • Key path: id
  • Type source: packages/core/src/types/storage.ts (Session)
  • Database version: wodwiki-db (v29)

Outcome of running one specific saved BlockRevision. Born status: 'in-progress' at workout start — the exact Note source/map, the revision row and this pin commit atomically before the runtime begins — and flipped to 'completed' when the lifecycle write finalizes (workout finished or user stopped early; completed records which). A session row is execution metadata only (V21): statements and metrics live as EventRecord rows, and display/replay shapes are reconstructed from them (eventsToStoredLogs). Replay reads the pinned revision; a duplicate source snapshot is unnecessary and absent.

Fields (Current)

Field Type Notes
id string UUID
noteId string FK → Note
blockId string Pinned occurrence identity → BlockRevision.blockId
blockVersion number Pinned saved version → BlockRevision.version
blockContentId? string Same-content history join with BlockIndexRow; not a foreign key or occurrence identifier
origin? ResultOrigin 'journal' | 'playground' | 'user'; playground excluded from default filters
status 'in-progress' | 'completed' in-progress until the finalize write commits
pageId? string @deprecated V10 legacy placement field (placements now owned by PageNote)
startTime number When the workout started (flattened from data in V21)
endTime number When the workout ended
duration number Total elapsed time (ms)
roundsCompleted? / totalRounds? number Rounds-based workouts
repsCompleted? number Rep-based workouts
completed boolean Finished vs stopped early
createdAt number When the session was captured

Indexes (Current)

Index Key path Unique Purpose
by-note noteId no per-note history
by-completed createdAt no recency ordering
by-content blockContentId no cross-workout joins (V6)
by-block blockId no occurrence identity (V6)
by-page pageId no legacy page index (V10)

Relationships (Current)

Outgoing (this row references)

  • noteId → Note — parent (deletion retains the Session and its pinned revision)
  • noteId + blockId + blockVersion → BlockRevision — pinned recorded occurrence/version, required
  • pageId → Page — legacy denormalized context
  • blockContentId → BlockIndexRow — content-hash join

Incoming (referenced by)

Relationship tables

Future State (Proposed)

Typed-note composition recommendations

These recommendations do not implement behavior or resolve a ticket; mode policy lives in Page#Mode and write destinations and identity questions in BlockRevision.

  • Saving a result is separate from editing note source. Run may be available in read presentation, but its owning note, occurrence/version and save destination must be explicit.
  • Preserve the two identity axes: a specific recorded occurrence/version versus intentional same-content history. Identical blocks do not share edit targets merely because their content IDs match.
  • Keep result identity stable between completion, persistence and any inserted session-results query. Read-only source must not be mutated just to display results; the host needs a permitted presentation/destination.
  • Do not derive result origin solely from a newly named note type or silently reassign history when a note moves between pages. Existing journal/playground filtering remains a compatibility constraint.
  • Canonical execution routes: browsing execution sessions lives at /sessions (with optional WQL query); session detail lives at /sessions/:sessionId; sessions from a specific date live at /session/:date. Legacy /results and /results/:resultId redirect to these routes.
  • Outgoing note links: links from a session record to its parent workout target /notes/:noteId (or /c/:slug/:page-slug for corpus items without stored note rows).

Feedback case: run the second of two identical workouts on a read-presented note. Where is the result stored and displayed if the source cannot accept a results-query insertion? The run must not overwrite seed content or attach to the first occurrence.

Implemented rename and flattening

Landed as its own cutover (commit 0988427e and the V21 migration). No compatibility aliases remain.

  • Store: sessions (renamed from results in V20; flattened in V21).
  • Entity: Session (renamed from WorkoutResult); UnifiedEventRecord → EventRecord.
  • Fields: the inline data payload is gone — scalars flattened onto the row, statements stored as EventRecord rows.
  • Ids: stored identifiers keep their historical names (resultId, field_sources prefix result:<id>, ${resultId}:${seq} row ids) because they are persisted keys, not vocabulary.

Map

!

Clone this wiki locally