[psharma-1909]

Summary

Aligns singlestore-nodejs with SingleStore Load Data from Local Files: LOAD DATA LOCAL INFILE already worked via infileStreamFactory; this PR adds in-memory streaming, an explicit local_infile connection option, fixes factory inheritance for prepared statements and pool cluster, and documents local-file vs in-memory loads.

Changes

Features

• infileStream (query option) — Stream bytes from a Node.js Readable for LOAD DATA LOCAL INFILE. The filename in SQL is ignored. Takes precedence over infileStreamFactory.
• local_infile (connection option) — Controls CLIENT_LOCAL_FILES (default true). When false, file and stream loads fail with a clear client error; relevant server errors (1148 / 3948 / 4166) are rewritten when appropriate.
• lib/commands/local_infile.js — Shared helpers for option assignment, disabled errors, and error rewriting.
• Query / Execute — Shared local-infile handling; connection-level factory used when the query does not set one.
• PreparedStatementInfo.execute — Passes connection infileStreamFactory into Execute.
• PoolCluster.query — Inherits connection-level infileStreamFactory when omitted on the query.

Types

• ConnectionOptions: local_infile
• QueryOptions: infileStream

Tests

• Unit: test/unit/commands/test-local-infile.test.cjs, test/unit/connection/test-connection_config.test.cjs, test/unit/pool-cluster/test-load-infile-factory.test.cjs
• Integration: extended test/integration/connection/test-load-infile.test.cjs (memory stream, local_infile: false)

Documentation

• README, site docs (extras, quickstart, API/config, indexes), Changelog unreleased 1.0.2, QueryOptions embed fixtures

---

Note

Medium Risk
Changes LOAD DATA LOCAL INFILE behavior (new in-memory path and client-side disable), which affects bulk ingest and a historically sensitive protocol feature, though defaults stay permissive and opt-out is explicit.

Overview
Adds in-memory bulk load for LOAD DATA LOCAL INFILE via a new query option infileStream (a Node Readable). When set, uploaded bytes come from that stream and the filename in SQL is ignored; infileStream wins over infileStreamFactory.

Introduces local_infile on the connection (default true), wired to CLIENT_LOCAL_FILES, with string/boolean parsing and interaction with flags. When disabled, loads fail early with a clear connector message, and selected server errors (1148 / 3948 / 4166) are rewritten for LOCAL INFILE SQL via shared lib/commands/local_infile.js.

Query and Execute share the same option assignment and streaming path (connection-level factory when the query omits one). Prepared statement execute and PoolCluster.query now propagate connection infileStreamFactory where it was missing before.

TypeScript adds local_infile and infileStream; README and site docs document file vs memory loads and fix singlestore-nodejs require examples. Unit and integration tests cover memory loads, disabled infile, config flags, and pool cluster inheritance.

^{Reviewed by Cursor Bugbot for commit ea2ab39. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit ea2ab39. Configure here.}

[cursor]

Execute skips LOCAL INFILE completion

High Severity

Execute now accepts infileStream and a connection infileStreamFactory, but it never copies infileOk from Query. After _streamLocalInfile sends file bytes it returns undefined, so the command emits end before the server OK. That desynchronizes the connection and can release a pooled connection while the stream is still writing.

Additional Locations (2)

• lib/commands/prepare.js#L27-L37
• lib/commands/execute.js#L30-L31

 

^{Reviewed by Cursor Bugbot for commit ea2ab39. Configure here.}

[cursor]

Approved. Cursor Bugbot was skipped and Cursor Security Agent did not run, so those signals were not used; no approval policy required human review and this automation had no prior approval. No reviewers were assigned.

  

_{Sent by Cursor Approval Agent: Pull Request Router and Approver}