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

    Interface DumpOptions

    options that shape a dump; a resumed export must repeat them

    interface DumpOptions {
        includeRows?: (table: string) => boolean;
        limitPerTable?: number;
        maxCharsPerChunk?: number;
        maxLiteralChars?: number;
        sealedRows?: readonly (readonly [string, string])[];
        secrets?: boolean;
    }
    Index
    includeRows?: (table: string) => boolean

    Rows-only filter, defaulting to !isRegenerable. DDL is always emitted, so a trimmed dump still restores the whole schema. Pass () => true for a byte-exact copy.

    limitPerTable?: number

    rows per table, for a cheap sample; 0 or absent is every row

    maxCharsPerChunk?: number

    characters per chunk for dumpChunk; see DUMP_CHARS_PER_CHUNK

    maxLiteralChars?: number

    Largest literal a single statement may carry before the value is built across appends.

    Well under the 100,000-character ceiling by default (the surrounding INSERT costs too).

    sealedRows?: readonly (readonly [string, string])[]

    Credentials held outside SQL, as [key, value]; emitted as cfw_meta rows with the dump's last statements when secrets is set, and moved back into sealed storage on import.

    secrets?: boolean

    carry SECRET_META_KEYS; a faithful restore needs them, a backup does not