ResultStreamObserver | /core/internal/observers.ts | neo4j_lite_client@4.4.6

Module

x/neo4j_lite_client/core/internal/observers.ts>ResultStreamObserver

Unofficial Neo4j Driver for Deno

bradenmacdonald/deno-neo4j-lite-client

Latest

resolver

index.ts (default module)

EMPTY_CONNECTION_HOLDER

connectivity-verifier.ts

DEFAULT_POOL_ACQUISITION_TIMEOUT

DEFAULT_POOL_MAX_SIZE

DAYS_PER_400_YEAR_CYCLE

NANOS_PER_MILLISECOND

NANOS_PER_MINUTE

NANOS_PER_SECOND

NANOSECOND_OF_SECOND_RANGE

SECOND_OF_MINUTE_RANGE

assertValidNanosecond

localDateTimeToEpochSecond

localTimeToNanoOfDay

normalizeNanosecondsForDuration

normalizeSecondsForDuration

timeToIsoString

timeZoneOffsetInSeconds

timeZoneOffsetToIsoString

totalNanoseconds

transaction-executor.ts

Url

assertNumberOrInteger

validateQueryAndParameters

interface ResultStreamObserver

implements StreamObserver

import { type ResultStreamObserver } from "https://deno.land/x/neo4j_lite_client@4.4.6/core/internal/observers.ts";

Raw observer for the stream

Methods

cancel(): void

Cancel pending record stream

prepareToHandleSingleResponse(): void

Stream observer defaults to handling responses for two messages: RUN + PULL_ALL or RUN + DISCARD_ALL. Response for RUN initializes query keys. Response for PULL_ALL / DISCARD_ALL exposes the result stream.

However, some operations can be represented as a single message which receives full metadata in a single response. For example, operations to begin, commit and rollback an explicit transaction use two messages in Bolt V1 but a single message in Bolt V3. Messages are RUN "BEGIN" {} + PULL_ALL in Bolt V1 and BEGIN in Bolt V3.