Skip to content

Engine: structured per-statement counts in write replies (EN-4) #257

Closed

Description

@jsam

Goal. Write replies report per-statement counts as structured data instead of message text.

Why. Callers (the gateway, both SDKs) must know whether a guarded update's token landed. Today they parse Update: N deleted, M inserted. text, and a program ending with a query loses the counts entirely.

In flight. PR #255 (draft): statements: [{index, kind, inserted, deleted}] on write replies.

Done when. #255 merges; the SDK compilers read counts from the field and drop the text grammar.

Plan reference: EN-4. Part of the Engine production readiness milestone (the current focus; tracker #199). Rule for every engine PR: millisecond query and update latency must not regress, and the perf gate runs before the PR opens.

Activity

  1. added
    backendBackend/server related
    P1Required next for reliable reactive delivery and operations
    on Oct 4, 2026
  2. jsam commented on Oct 5, 2026

    @jsam
    ContributorAuthor

    Done in #255 (merged): structured per-statement results in write replies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1Required next for reliable reactive delivery and operationsbackendBackend/server related

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions