drupflare/worker - v1.0.4
    Preparing search index...

    Interface DumpResult

    the whole dump and its accounting

    interface DumpResult {
        chars: number;
        maxStatementChars: number;
        offsetPaged: string[];
        redacted: number;
        replayable: boolean;
        splitValues: number;
        sql: string;
        statements: number;
        structureOnly: string[];
        tables: Record<string, number>;
    }
    Index
    chars maxStatementChars offsetPaged redacted replayable splitValues sql statements structureOnly tables
    chars: number

    characters, not bytes (a UTF-8 literal is wider on the wire)

    maxStatementChars: number

    The widest single statement, for judging whether the dump can be replayed.

    A Durable Object caps statement text at 100,000 characters, and /export?all=1 can emit a 960,544-character cache_container row that stores fine and fails mid-restore.

    offsetPaged: string[]

    Tables paged by OFFSET because they are WITHOUT ROWID.

    OFFSET paging re-scans and can repeat or skip a row if the site writes mid-export. Empty on every schema this ships with.

    redacted: number

    rows withheld by SECRET_META_KEYS; a dump must say what it is not carrying

    replayable: boolean

    false when any statement exceeds the ceiling, so a caller can refuse before storing it

    splitValues: number

    values too wide for one statement, rebuilt with col = col || ... appends

    sql: string
    statements: number
    structureOnly: string[]

    The tables emitted structure-only, resolved from REGENERABLE_TABLES so a report cannot go stale when the list changes.

    tables: Record<string, number>

    rows emitted per table, including the tables that emitted none

    Settings
    Member Visibility

    On This Page
    Properties