turbine-orm 0.77.1 → 0.78.0

package/dist/cjs/cli/sql-statements.js

@@ -238,6 +238,32 @@ function tokenizeSql(sql) {
         }
         // Single-quoted literal. `''` always escapes a quote; inside an E-string a
         // backslash escapes the next character too.
+        //
+        // The CONTENT is handed over as a block, exactly as a dollar-quoted body
+        // is. A routine body does not have to be dollar-quoted: `DO 'BEGIN DROP
+        // TABLE users; END'` and `CREATE FUNCTION f() ... AS 'DELETE FROM t'` are
+        // both ordinary PostgreSQL and both execute. This branch used to push
+        // NOTHING, so `SqlStatement.blocks` came back empty for them, and the
+        // destructive scanner iterates `procedural ? statement.blocks : []`: with
+        // no blocks, every procedural pass was skipped, INCLUDING the fail-closed
+        // "cannot classify" backstop. The statement was correctly recognized as
+        // procedural and then scanned against nothing, so the guard reported a
+        // clean inventory for a file that drops a table. Verified live before the
+        // fix on PostgreSQL 17: no prompt, no `--allow-destructive`, table gone.
+        //
+        // Handing over EVERY single-quoted literal, not only the ones in a
+        // procedural statement, is deliberate and costs nothing: this tokenizer
+        // does not know which statement it is in the middle of, the consumer
+        // already gates on `PROCEDURAL_STATEMENT`, and pushing more is the
+        // fail-CLOSED direction this file resolves ambiguity toward. `INSERT INTO
+        // log VALUES ('DROP TABLE x')` is unaffected because an INSERT is not
+        // procedural, which is the same reason the dollar-quoted branch above can
+        // push unconditionally.
+        //
+        // `''` is unescaped to `'` so the block lexes as the SQL it will BE when
+        // the server reads it: the payload of `DO 'BEGIN EXECUTE ''DROP TABLE
+        // t''; END'` is `EXECUTE 'DROP TABLE t'`, and a nested scan of the raw
+        // slice would see a doubled quote where a string opener belongs.
         if (ch === "'") {
             const escapes = isEscapeStringPrefix(sql, i);
             let j = i + 1;
@@ -255,6 +281,7 @@ function tokenizeSql(sql) {
                 j++;
             }
             const end = Math.min(j + 1, n);
+            blocks.push(sql.slice(i + 1, Math.min(j, n)).replace(/''/g, "'"));
             stripped += "''";
             code += sql.slice(i, end);
             i = end;

package/dist/cjs/cli/studio.d.ts

@@ -196,7 +196,6 @@ export declare function relationLinksForTable(table: TableMetadata, metadata: Sc
 export declare function apiTableRows(res: ServerResponse, ctx: StudioContext, rawTableName: string, params: URLSearchParams): Promise<void>;
 export declare function resolveColumnName(table: TableMetadata, nameOrField: string): string | null;
 export declare function isTextishType(pgType: string): boolean;
-export declare function escapeLikePattern(s: string): string;
 export declare function apiBuilder(req: IncomingMessage, res: ServerResponse, ctx: StudioContext): Promise<void>;
 export declare function apiRowWrite(req: IncomingMessage, res: ServerResponse, ctx: StudioContext, op: 'update' | 'insert' | 'delete'): Promise<void>;
 interface SavedQuery {

package/dist/cjs/cli/studio.js

@@ -49,7 +49,6 @@ exports.relationLinksForTable = relationLinksForTable;
 exports.apiTableRows = apiTableRows;
 exports.resolveColumnName = resolveColumnName;
 exports.isTextishType = isTextishType;
-exports.escapeLikePattern = escapeLikePattern;
 exports.apiBuilder = apiBuilder;
 exports.apiRowWrite = apiRowWrite;
 exports.apiListSavedQueries = apiListSavedQueries;
@@ -598,12 +597,19 @@ async function apiTableRows(res, ctx, rawTableName, params) {
     // Full-text-ish search: ILIKE across text/varchar columns. The value is
     // parameterized so injection is impossible. Each query gets its own
     // WHERE clause with parameter indices matching that query's param array.
+    // LIKE operands go through the dialect's escaper, the same hook the query
+    // builder uses (`Dialect.escapeLikePattern`): which characters need escaping
+    // is a property of the engine's pattern grammar, not of this SQL text, and a
+    // private copy here is how Studio came to bypass the SQL Server rule for
+    // `[`. No hook (Postgres, and the demo's SQLite, which inherits none) means
+    // the shared default. Paired with the `ESCAPE '\'` clause `likeCond` emits.
+    const escapeLikeOperand = (v) => ctx.dialect?.escapeLikePattern?.(v) ?? (0, utils_js_1.escapeLike)(v);
     const search = params.get('search')?.trim() ?? '';
     const textColumns = table.columns
         .filter((c) => isTextishType(c.pgType) && !redactedPii.has(c.name))
         .map((c) => c.name);
     const hasSearch = search.length > 0 && textColumns.length > 0;
-    const pattern = hasSearch ? `%${escapeLikePattern(search)}%` : null;
+    const pattern = hasSearch ? `%${escapeLikeOperand(search)}%` : null;
     // Per-column filters: `filters` is a JSON array of { column, op, value }
     // composed by the Data tab's filter bar. Every column is validated against
     // the metadata, every op against a fixed whitelist, and every value is a
@@ -646,7 +652,7 @@ async function apiTableRows(res, ctx, rawTableName, params) {
                 conds.push(`${(0, index_js_1.quoteIdent)(f.column)} IS NOT NULL`);
             }
             else if (f.op === 'contains') {
-                values.push(`%${escapeLikePattern(String(f.value))}%`);
+                values.push(`%${escapeLikeOperand(String(f.value))}%`);
                 conds.push(likeCond(f.column, n++));
             }
             else {
@@ -729,10 +735,6 @@ function isTextishType(pgType) {
         pgType === 'citext' ||
         pgType === 'uuid');
 }
-function escapeLikePattern(s) {
-    // Escape the LIKE wildcards so user input is treated literally.
-    return s.replace(/\\/g, '\\\\').replace(/%/g, '\\%').replace(/_/g, '\\_');
-}
 // ---------------------------------------------------------------------------
 // Data-tab per-column filters
 // ---------------------------------------------------------------------------

package/dist/cjs/client.d.ts

@@ -959,6 +959,13 @@ export declare class TurbineClient {
      * replicas are configured this simply returns the client itself (already
      * primary-only). The view is cached, repeated calls return the same instance.
      *
+     * Typed as `this` so a generated subclass keeps its declared table accessors
+     * through the call (`db.$primary().users`, the form in the example below).
+     * With the base class as the return type the accessors were gone and the only
+     * typed route was `db.$primary().table('users')`. The view is a base-class
+     * instance built from the same schema, so at runtime it carries every table
+     * accessor the subclass `declare`s; the cast states exactly that.
+     *
      * @example
      * ```ts
      * await db.users.create({ data: { email: 'a@b.com' } });
@@ -966,7 +973,7 @@ export declare class TurbineClient {
      * const user = await db.$primary().users.findFirst({ where: { email: 'a@b.com' } });
      * ```
      */
-    $primary(): TurbineClient;
+    $primary(): this;
     /**
      * Execute multiple queries in a single database round-trip.
      *

package/dist/cjs/client.js

@@ -1459,6 +1459,13 @@ class TurbineClient {
      * replicas are configured this simply returns the client itself (already
      * primary-only). The view is cached, repeated calls return the same instance.
      *
+     * Typed as `this` so a generated subclass keeps its declared table accessors
+     * through the call (`db.$primary().users`, the form in the example below).
+     * With the base class as the return type the accessors were gone and the only
+     * typed route was `db.$primary().table('users')`. The view is a base-class
+     * instance built from the same schema, so at runtime it carries every table
+     * accessor the subclass `declare`s; the cast states exactly that.
+     *
      * @example
      * ```ts
      * await db.users.create({ data: { email: 'a@b.com' } });

package/dist/cjs/connection-url.d.ts

@@ -188,3 +188,85 @@ export declare function withStatementTimeoutOption(config: ConnectionOptionsConf
  * the cycle `scripts/check-import-cycles.mjs` exists to refuse.
  */
 export declare function mergeConnectionStringOptions(connectionString: string, setting: string): string | null;
+/**
+ * The schema names {@link withSearchPathOption} accepts: a plain SQL
+ * identifier, letters, digits, `_` and `$`, not starting with a digit.
+ *
+ * Deliberately narrower than what Postgres allows in a quoted identifier. A GUC
+ * value cannot be a bind parameter, so the emitted text necessarily contains
+ * the caller's string as a literal, and the libpq `options` parameter is split
+ * on WHITESPACE: a name that can carry a space can carry a second `-c` and set
+ * any backend GUC it likes. Refusing anything outside this alphabet is what
+ * makes the literal safe to emit, the same reasoning as the integer narrowing in
+ * {@link withStatementTimeoutOption}.
+ */
+export declare const SEARCH_PATH_SCHEMA_PATTERN: RegExp;
+/** Whether `schema` is a name {@link withSearchPathOption} will emit. */
+export declare function isPlainSchemaIdentifier(schema: string): boolean;
+/**
+ * The schema names in a `SHOW search_path` value, unquoted.
+ *
+ * Postgres renders the GUC as a comma-separated identifier list, quoting only
+ * the entries that need it, so this splits on commas OUTSIDE double quotes and
+ * un-doubles `""`. Anything the caller cannot safely re-emit is dropped by
+ * {@link searchPathListValue}, not here: this function's job is to say what the
+ * connection's path IS.
+ */
+export declare function parseSearchPathValue(shown: string): string[];
+/**
+ * `connectionString` with `search_path` pinned to `schema` through the
+ * connection's **startup parameters** (`options=-c search_path="<schema>"`),
+ * never through a `SET`.
+ *
+ * This is the mechanism a tool that emits UNQUALIFIED identifiers uses to land
+ * them in the configured schema: the migration runner (`CREATE TABLE t1` from a
+ * migration file, and its own `_turbine_migrations` tracking table) and the seed
+ * runner both connect through it. The alternative, `SET search_path` after
+ * connecting, is exactly the session-state write a transaction pooler leaves
+ * behind on a shared backend, see the module comment. The startup parameter is
+ * in force for the connection's first statement and cannot outlive it.
+ *
+ * The schema is QUOTED inside the GUC value. Postgres parses `search_path` as
+ * an identifier list and folds an unquoted entry to lower case, so an unquoted
+ * `MySchema` would resolve to `myschema`, while every other place this CLI
+ * reads the configured name (introspection's `table_schema = $1`, the push
+ * pin) treats it exactly. Quoting keeps the three in agreement. The quotes are
+ * safe to emit because {@link SEARCH_PATH_SCHEMA_PATTERN} admits no `"` and no
+ * whitespace; anything else throws rather than reaching the wire.
+ *
+ * The value EXTENDS the caller's path rather than discarding it: `schema` goes
+ * FIRST (an unqualified CREATE uses the first entry, which is the whole point of
+ * the pin) and every name in `alsoResolveIn` follows. Pinning used to emit the
+ * target ALONE, which is a different behaviour from the push path's
+ * `pinSearchPath`, and the difference is not cosmetic: on the ordinary managed
+ * layout (`public, extensions`) a `citext` / `vector` / `hstore` / `postgis`
+ * column, an extension opclass in a CREATE INDEX, or a CHECK calling an
+ * extension function all failed under a pin that the same DDL did not need
+ * without one. Two authorities on one question, so there is now one.
+ *
+ * The inherited path cannot be read before the connection exists, so
+ * `alsoResolveIn` is the caller's job: connect once unpinned, `SHOW
+ * search_path`, hand the names here (see {@link parseSearchPathValue}). Nothing
+ * is guessed, and an empty list emits exactly what it always did.
+ *
+ * Merge rules match {@link withStatementTimeoutOption}: an existing
+ * `?options=` is appended to (the later `-c search_path` wins on the backend),
+ * an existing query string gains an `options` entry, and a bare URL gains
+ * `?options=`. In the two branches that CREATE the parameter, `PGOPTIONS` is
+ * folded in first: pg reads the environment variable only while the connection
+ * carries no `options` of its own, so adding one blind would silently drop a
+ * deployment's setting. Only a URL-shaped string is rewritten; a key/value DSN
+ * (which node-postgres does not parse anyway) yields `null` instead of being
+ * returned unchanged.
+ *
+ * Returns `null`, never a guess, when it cannot pin SAFELY: a schema outside
+ * {@link SEARCH_PATH_SCHEMA_PATTERN}, or a connection string that is not a
+ * URL. This module raises nothing because it imports nothing (`ValidationError`
+ * included, see the module comment on why it must stay a leaf), the same
+ * posture as {@link withStatementTimeoutOption} returning its input untouched
+ * on a bad timeout. The caller owns the refusal and its error code
+ * (`connectionStringForSchema` in cli/migrate.ts raises E003), and MUST treat
+ * `null` as a refusal: the unpinned string means "into whichever schema the
+ * role defaults to", the exact outcome this exists to prevent.
+ */
+export declare function withSearchPathOption(connectionString: string, schema: string, alsoResolveIn?: readonly string[]): string | null;

package/dist/cjs/connection-url.js

@@ -34,12 +34,15 @@
  * command from reporting confidently about a connection it cannot reason about.
  */
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.POOLER_PORTS = exports.POOLER_HOST_TOKENS = void 0;
+exports.SEARCH_PATH_SCHEMA_PATTERN = exports.POOLER_PORTS = exports.POOLER_HOST_TOKENS = void 0;
 exports.parseConnectionTarget = parseConnectionTarget;
 exports.detectPooler = detectPooler;
 exports.poolerRefusalMessage = poolerRefusalMessage;
 exports.withStatementTimeoutOption = withStatementTimeoutOption;
 exports.mergeConnectionStringOptions = mergeConnectionStringOptions;
+exports.isPlainSchemaIdentifier = isPlainSchemaIdentifier;
+exports.parseSearchPathValue = parseSearchPathValue;
+exports.withSearchPathOption = withSearchPathOption;
 /**
  * Host and port from a connection string, in either shape libpq accepts.
  *
@@ -292,3 +295,186 @@ function mergeConnectionStringOptions(connectionString, setting) {
     params.set('options', `${existing} ${setting}`);
     return connectionString.slice(0, q + 1) + params.toString();
 }
+// ---------------------------------------------------------------------------
+// Connection-time search_path
+// ---------------------------------------------------------------------------
+/**
+ * The schema names {@link withSearchPathOption} accepts: a plain SQL
+ * identifier, letters, digits, `_` and `$`, not starting with a digit.
+ *
+ * Deliberately narrower than what Postgres allows in a quoted identifier. A GUC
+ * value cannot be a bind parameter, so the emitted text necessarily contains
+ * the caller's string as a literal, and the libpq `options` parameter is split
+ * on WHITESPACE: a name that can carry a space can carry a second `-c` and set
+ * any backend GUC it likes. Refusing anything outside this alphabet is what
+ * makes the literal safe to emit, the same reasoning as the integer narrowing in
+ * {@link withStatementTimeoutOption}.
+ */
+exports.SEARCH_PATH_SCHEMA_PATTERN = /^[A-Za-z_][A-Za-z0-9_$]*$/;
+/** Whether `schema` is a name {@link withSearchPathOption} will emit. */
+function isPlainSchemaIdentifier(schema) {
+    return exports.SEARCH_PATH_SCHEMA_PATTERN.test(schema);
+}
+/**
+ * The one name outside {@link SEARCH_PATH_SCHEMA_PATTERN} that is still safe to
+ * emit into the `options=-c` literal, and worth keeping.
+ *
+ * `$user` is Postgres's own token for "the schema named after the current
+ * role", and it leads the default `search_path` on nearly every installation.
+ * The pattern refuses it because a name may not START with `$`, which is right
+ * for a CALLER-supplied schema; dropping it from an inherited path, however,
+ * silently changes name resolution. It carries no whitespace, no quote and no
+ * backslash, so it cannot smuggle a second `-c`, which is the only property the
+ * literal needs.
+ */
+const SEARCH_PATH_USER_TOKEN = '$user';
+/**
+ * The schema names in a `SHOW search_path` value, unquoted.
+ *
+ * Postgres renders the GUC as a comma-separated identifier list, quoting only
+ * the entries that need it, so this splits on commas OUTSIDE double quotes and
+ * un-doubles `""`. Anything the caller cannot safely re-emit is dropped by
+ * {@link searchPathListValue}, not here: this function's job is to say what the
+ * connection's path IS.
+ */
+function parseSearchPathValue(shown) {
+    const names = [];
+    let current = '';
+    let quoted = false;
+    let sawContent = false;
+    for (let i = 0; i < shown.length; i++) {
+        const ch = shown[i];
+        if (quoted) {
+            if (ch === '"') {
+                if (shown[i + 1] === '"') {
+                    current += '"';
+                    i++;
+                }
+                else {
+                    quoted = false;
+                }
+            }
+            else {
+                current += ch;
+            }
+            continue;
+        }
+        if (ch === '"') {
+            quoted = true;
+            sawContent = true;
+            continue;
+        }
+        if (ch === ',') {
+            const name = current.trim();
+            if (name !== '' || sawContent)
+                names.push(name);
+            current = '';
+            sawContent = false;
+            continue;
+        }
+        current += ch;
+    }
+    const last = current.trim();
+    if (last !== '' || sawContent)
+        names.push(last);
+    return names.filter((n) => n !== '');
+}
+/**
+ * The `search_path` GUC value a pin emits: `schema` first, then each name in
+ * `alsoResolveIn` that survives the same validation `schema` did.
+ *
+ * Every entry is quoted (Postgres folds an unquoted one to lower case, and the
+ * rest of the CLI treats the configured name exactly), and the list is joined
+ * with a BARE comma: the libpq `options` parameter is split on WHITESPACE, so a
+ * space inside the value would start a second `-c`. A name that cannot be
+ * emitted safely is DROPPED rather than escaped, because the alternative is
+ * inventing an escaping rule for a literal whose only defence is its alphabet.
+ * Dropping is monotone against the previous behaviour, which dropped all of
+ * them.
+ */
+function searchPathListValue(schema, alsoResolveIn) {
+    const seen = new Set([schema]);
+    const names = [schema];
+    for (const name of alsoResolveIn) {
+        if (seen.has(name))
+            continue;
+        if (!isPlainSchemaIdentifier(name) && name !== SEARCH_PATH_USER_TOKEN)
+            continue;
+        seen.add(name);
+        names.push(name);
+    }
+    return names.map((n) => `"${n}"`).join(',');
+}
+/**
+ * `connectionString` with `search_path` pinned to `schema` through the
+ * connection's **startup parameters** (`options=-c search_path="<schema>"`),
+ * never through a `SET`.
+ *
+ * This is the mechanism a tool that emits UNQUALIFIED identifiers uses to land
+ * them in the configured schema: the migration runner (`CREATE TABLE t1` from a
+ * migration file, and its own `_turbine_migrations` tracking table) and the seed
+ * runner both connect through it. The alternative, `SET search_path` after
+ * connecting, is exactly the session-state write a transaction pooler leaves
+ * behind on a shared backend, see the module comment. The startup parameter is
+ * in force for the connection's first statement and cannot outlive it.
+ *
+ * The schema is QUOTED inside the GUC value. Postgres parses `search_path` as
+ * an identifier list and folds an unquoted entry to lower case, so an unquoted
+ * `MySchema` would resolve to `myschema`, while every other place this CLI
+ * reads the configured name (introspection's `table_schema = $1`, the push
+ * pin) treats it exactly. Quoting keeps the three in agreement. The quotes are
+ * safe to emit because {@link SEARCH_PATH_SCHEMA_PATTERN} admits no `"` and no
+ * whitespace; anything else throws rather than reaching the wire.
+ *
+ * The value EXTENDS the caller's path rather than discarding it: `schema` goes
+ * FIRST (an unqualified CREATE uses the first entry, which is the whole point of
+ * the pin) and every name in `alsoResolveIn` follows. Pinning used to emit the
+ * target ALONE, which is a different behaviour from the push path's
+ * `pinSearchPath`, and the difference is not cosmetic: on the ordinary managed
+ * layout (`public, extensions`) a `citext` / `vector` / `hstore` / `postgis`
+ * column, an extension opclass in a CREATE INDEX, or a CHECK calling an
+ * extension function all failed under a pin that the same DDL did not need
+ * without one. Two authorities on one question, so there is now one.
+ *
+ * The inherited path cannot be read before the connection exists, so
+ * `alsoResolveIn` is the caller's job: connect once unpinned, `SHOW
+ * search_path`, hand the names here (see {@link parseSearchPathValue}). Nothing
+ * is guessed, and an empty list emits exactly what it always did.
+ *
+ * Merge rules match {@link withStatementTimeoutOption}: an existing
+ * `?options=` is appended to (the later `-c search_path` wins on the backend),
+ * an existing query string gains an `options` entry, and a bare URL gains
+ * `?options=`. In the two branches that CREATE the parameter, `PGOPTIONS` is
+ * folded in first: pg reads the environment variable only while the connection
+ * carries no `options` of its own, so adding one blind would silently drop a
+ * deployment's setting. Only a URL-shaped string is rewritten; a key/value DSN
+ * (which node-postgres does not parse anyway) yields `null` instead of being
+ * returned unchanged.
+ *
+ * Returns `null`, never a guess, when it cannot pin SAFELY: a schema outside
+ * {@link SEARCH_PATH_SCHEMA_PATTERN}, or a connection string that is not a
+ * URL. This module raises nothing because it imports nothing (`ValidationError`
+ * included, see the module comment on why it must stay a leaf), the same
+ * posture as {@link withStatementTimeoutOption} returning its input untouched
+ * on a bad timeout. The caller owns the refusal and its error code
+ * (`connectionStringForSchema` in cli/migrate.ts raises E003), and MUST treat
+ * `null` as a refusal: the unpinned string means "into whichever schema the
+ * role defaults to", the exact outcome this exists to prevent.
+ */
+function withSearchPathOption(connectionString, schema, alsoResolveIn = []) {
+    if (!isPlainSchemaIdentifier(schema))
+        return null;
+    const setting = `-c search_path=${searchPathListValue(schema, alsoResolveIn)}`;
+    const merged = mergeConnectionStringOptions(connectionString, setting);
+    if (merged !== null)
+        return merged;
+    if (!/^[a-z][a-z0-9+.-]*:\/\//i.test(connectionString.trim()))
+        return null;
+    const pgOptions = typeof process !== 'undefined' ? process.env?.PGOPTIONS : undefined;
+    const value = pgOptions ? `${pgOptions} ${setting}` : setting;
+    const q = connectionString.indexOf('?');
+    const params = new URLSearchParams(q === -1 ? '' : connectionString.slice(q + 1));
+    params.set('options', value);
+    const head = q === -1 ? connectionString : connectionString.slice(0, q);
+    return `${head}?${params.toString()}`;
+}