@vantreeseba/drizzle-graphql 5.4.0 → 5.5.0

package/dist/index.d.cts

@@ -693,6 +693,40 @@ type BuildSchemaConfig = {
      * queries are always generated, so `Query` is never empty.
      */
     features?: SchemaFeatures;
+    /**
+     * Automatic transactions for GraphQL documents that fire more than one mutation.
+     *
+     * `'none'` (default) — every root mutation field runs on its own connection, so a failure
+     * mid-document leaves the earlier mutations committed (today's behavior).
+     *
+     * `'auto'` — when a request's document selects more than one root mutation field, the
+     * library opens `db.transaction()` once for the whole request and runs every mutation
+     * field (and the reads nested under them) inside it. The transaction commits when the
+     * last mutation field completes and rolls back when any of them fails; mutation fields
+     * after a failure are not executed against the rolled-back transaction — they fail fast.
+     * The object form additionally sets the safety timeout (default 30000ms) after which an
+     * abandoned transaction — e.g. the host server stopped calling resolvers because of a
+     * non-null completion error — is rolled back instead of leaking a connection.
+     *
+     * Never nests: a caller-supplied executor on the GraphQL context under
+     * `drizzleExecutorKey` always wins, and the library opens nothing of its own.
+     *
+     * Requirements and caveats:
+     * - The driver must support `db.transaction()` (e.g. `neon-http` does not). For SQLite
+     *   only asynchronous drivers (libsql, better-sqlite3 is synchronous) can hold a
+     *   transaction open across resolvers; `buildSchema` throws for synchronous ones.
+     * - The GraphQL context value must be a fresh object per request (every mainstream
+     *   server does this) — it keys the per-request transaction state.
+     * - Documents that mix in mutation fields not generated by this build (consumer
+     *   extensions) are left alone: their completion cannot be tracked, so no transaction
+     *   is opened.
+     *
+     * @default 'none'
+     */
+    transactions?: 'auto' | 'none' | {
+        mode: 'auto';
+        timeoutMs?: number;
+    };
     /**
      * Optional mapper from table key to singular/plural name pair.
      * When provided for a table, overrides the default (table key) naming for GraphQL type names,

package/dist/index.d.ts

@@ -693,6 +693,40 @@ type BuildSchemaConfig = {
      * queries are always generated, so `Query` is never empty.
      */
     features?: SchemaFeatures;
+    /**
+     * Automatic transactions for GraphQL documents that fire more than one mutation.
+     *
+     * `'none'` (default) — every root mutation field runs on its own connection, so a failure
+     * mid-document leaves the earlier mutations committed (today's behavior).
+     *
+     * `'auto'` — when a request's document selects more than one root mutation field, the
+     * library opens `db.transaction()` once for the whole request and runs every mutation
+     * field (and the reads nested under them) inside it. The transaction commits when the
+     * last mutation field completes and rolls back when any of them fails; mutation fields
+     * after a failure are not executed against the rolled-back transaction — they fail fast.
+     * The object form additionally sets the safety timeout (default 30000ms) after which an
+     * abandoned transaction — e.g. the host server stopped calling resolvers because of a
+     * non-null completion error — is rolled back instead of leaking a connection.
+     *
+     * Never nests: a caller-supplied executor on the GraphQL context under
+     * `drizzleExecutorKey` always wins, and the library opens nothing of its own.
+     *
+     * Requirements and caveats:
+     * - The driver must support `db.transaction()` (e.g. `neon-http` does not). For SQLite
+     *   only asynchronous drivers (libsql, better-sqlite3 is synchronous) can hold a
+     *   transaction open across resolvers; `buildSchema` throws for synchronous ones.
+     * - The GraphQL context value must be a fresh object per request (every mainstream
+     *   server does this) — it keys the per-request transaction state.
+     * - Documents that mix in mutation fields not generated by this build (consumer
+     *   extensions) are left alone: their completion cannot be tracked, so no transaction
+     *   is opened.
+     *
+     * @default 'none'
+     */
+    transactions?: 'auto' | 'none' | {
+        mode: 'auto';
+        timeoutMs?: number;
+    };
     /**
      * Optional mapper from table key to singular/plural name pair.
      * When provided for a table, overrides the default (table key) naming for GraphQL type names,