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

    Module ops/write-forwarding

    How a lane accepts a write without committing it: run it locally, keep the statement list, roll back, and forward the list to the primary, which sequences the commit.

    Two hazards survive that, and they are treated differently:

    • origination: the statement mints a value two objects would mint differently (an id from sequences, system.private_key); no ordering rule repairs it
    • ordering: the statement updates something with a prior state, a lost update the log's parent generation already detects
    ForwardPlan
    ForwardStatement
    Hazard
    ID_PARTITION_LANES
    LANE_HIGH_PREFIX
    cacheTagIncrement
    deferrable
    hazardClass
    idStride
    keyValueTarget
    laneHighWater
    nextLaneId
    partitionedTables
    planForward
    splitForward
    writeForwardEnabled