@voltro/database 0.22.1 → 0.24.0

package/dist/index.d.ts

@@ -1404,6 +1404,31 @@ export declare interface ConnectionConfig {
      */
     readonly ssl?: boolean;
     readonly maxConnections?: number;
+    /**
+     * Per-statement timeout in ms — a runaway query (missing index, cartesian
+     * join) is aborted instead of holding a pooled connection forever, which under
+     * load exhausts the pool and stalls the whole app. Applied at the CONNECTION
+     * level so every query is bounded (no per-call opt-in). Env `DB_STATEMENT_TIMEOUT_MS`.
+     * Runtime-path only — the migration path (`voltro db apply`) deliberately does
+     * NOT read this, so a long backfill / index build is never cancelled by the app
+     * query ceiling.
+     *
+     * **Wired for postgres only** (the default dialect), enforced server-side via
+     * node-postgres' `statement_timeout` pool option — a runaway query is cancelled
+     * with SQLSTATE 57014, not merely disconnected. Every OTHER dialect currently
+     * ACCEPTS the field but IGNORES it, and the honest reasons differ:
+     *   - **mssql** — `@effect/sql-mssql` exposes only `connectTimeout` (connection
+     *     establishment), not tedious's per-request `requestTimeout`; mapping this
+     *     onto `connectTimeout` would bound the wrong phase, so it is left unwired
+     *     rather than wrong.
+     *   - **mysql/mariadb** — the server's `max_execution_time` bounds SELECTs only
+     *     (writes run unbounded), so a connection-level setting would be a partial,
+     *     misleading guarantee; not wired in V1.
+     *   - **sqlite** — in-process, one connection, no pool to exhaust; nothing to
+     *     protect.
+     * Unset (or any non-postgres dialect) = no timeout — behaviour is unchanged.
+     */
+    readonly statementTimeoutMs?: number;
     /**
      * Postgres only: the schema the app's tables live in, pinned as the
      * connection `search_path` (env `DB_SCHEMA`). When set, EVERY pooled
@@ -2308,6 +2333,17 @@ declare interface FormatIssueOptions {
     readonly indent?: string;
 }
 
+/**
+ * Live tables the framework's own runtime creates under a name that does NOT
+ * start with a reserved prefix, so the prefix rule below cannot recognise them.
+ *
+ * Public because consumers need to tell "a table the app declares" from "one the
+ * framework or a plugin brought" — `plugin-versioning` reads it to decide its
+ * default watch set. One copy of that rule on purpose: a second copy of it is
+ * how a per-dialect difference in what `voltro dev` does got shipped once.
+ */
+export declare const FRAMEWORK_LIVE_TABLES: ReadonlySet<string>;
+
 /** All framework tables as an array — useful for bootstrap DDL emission. */
 export declare const frameworkTables: readonly [TableLike, TableLike, TableLike];
 
@@ -2686,6 +2722,10 @@ export declare const isFieldDecryptionError: (e: unknown) => e is FieldDecryptio
 /** Type-guard for the discovery walker. */
 export declare const isFileMigration: (value: unknown) => value is FileMigration;
 
+/** True when `name` is a live table the framework / its runtime engines create
+ *  but no user schema declares — never plan a drop for it. */
+export declare const isFrameworkOwnedLiveTable: (name: string) => boolean;
+
 export declare const isMigrationDefinition: (value: unknown) => value is MigrationDefinition;
 
 /**