Prometheus Entity Management API
    Preparing search index...
    interface ChangeSet<T = Record<string, unknown>> {
        affectedListKeys?: string[];
        changes: EntityChange<T>[];
        cursor?: { handle: string; offset: string };
        timestamp?: string;
    }

    Type Parameters

    • T = Record<string, unknown>
    Index
    affectedListKeys?: string[]
    changes: EntityChange<T>[]
    cursor?: { handle: string; offset: string }

    The transport's resume position for this batch, when it has one.

    For ElectricSQL this is the shape handle plus the offset of the last message in the batch — the pair a consumer echoes back to resume. It is batch-level, not per-change: a resume position describes a boundary between batches, not a point inside one.

    Absent for transports with no resume semantics (a Postgres LISTEN/NOTIFY frame, for instance, carries no Electric offset). Absent is meaningful — it means "this batch cannot be checkpointed", not "offset zero".

    timestamp?: string