@molecule/api-database 1.0.2 → 1.1.0

package/LICENSE

@@ -1,3 +1,4 @@
+
                                  Apache License
                            Version 2.0, January 2004
                         http://www.apache.org/licenses/
@@ -34,21 +35,33 @@
 
       "Work" shall mean the work of authorship, whether in Source or
       Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work.
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
 
       "Derivative Works" shall mean any work, whether in Source or Object
       form, that is based on (or derived from) the Work and for which the
       editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship.
-
-      "Contribution" shall mean any work of authorship, including the
-      original version of the Work and any modifications or additions
-      to that Work, that is intentionally submitted to the Licensor for
-      inclusion in the Work by the copyright owner or by an individual or
-      Legal Entity authorized to submit on behalf of the copyright owner.
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
 
       "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by the Licensor and
+      on behalf of whom a Contribution has been received by Licensor and
       subsequently incorporated within the Work.
 
    2. Grant of Copyright License. Subject to the terms and conditions of
@@ -61,8 +74,18 @@
    3. Grant of Patent License. Subject to the terms and conditions of
       this License, each Contributor hereby grants to You a perpetual,
       worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      patent license to make, have made, use, offer to sell, sell, import,
-      and otherwise transfer the Work.
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
 
    4. Redistribution. You may reproduce and distribute copies of the
       Work or Derivative Works thereof in any medium, with or without
@@ -84,23 +107,87 @@
       (d) If the Work includes a "NOTICE" text file as part of its
           distribution, then any Derivative Works that You distribute must
           include a readable copy of the attribution notices contained
-          within such NOTICE file.
-
-   5. Submission of Contributions.
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
 
    6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor.
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
 
    7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND.
-
-   8. Limitation of Liability. In no event and under no legal theory shall
-      any Contributor be liable to You for damages.
-
-   9. Accepting Warranty or Additional Liability.
-
-   Copyright 2026 Molecule Dev, Inc.
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.

package/README.md

@@ -3,7 +3,7 @@ AUTO-GENERATED — DO NOT EDIT THIS FILE.
 Generated by `mlcl sync-docs` from the package's src/index.ts JSDoc + mlcl/registry.json.
 Edits here are overwritten on the next commit (molecule's pre-commit hook regenerates).
 To change this document, edit the module-level JSDoc in src/index.ts.
-Generated: 2026-08-06T03:43:57.387Z
+Generated: 2026-10-15T12:34:32.789Z
 -->
 
 # @molecule/api-database
@@ -534,6 +534,18 @@ function findOne(table: string, where: WhereCondition[]): Promise<T | null>
 
 **Returns:** The matching record cast to `T`, or `null` if none found.
 
+#### `getActiveTransaction()`
+
+The transaction opened by the enclosing `withTransaction()` call, if any.
+Bond pools call this from `query()` and send the statement to the active
+transaction when it is one they opened.
+
+```typescript
+function getActiveTransaction(): DatabaseTransaction | undefined
+```
+
+**Returns:** The active transaction, or `undefined` outside `withTransaction()`.
+
 #### `getPool()`
 
 Retrieves the bonded database pool, throwing if none is configured.
@@ -646,12 +658,39 @@ function updateMany(
 
 **Returns:** A `MutationResult` with the affected count.
 
+#### `withTransaction(fn)`
+
+Runs `fn` inside one database transaction: commits when it resolves, rolls
+back and rethrows when it throws. Every database call made while `fn` runs
+joins the transaction — `create`/`findMany`/`updateById`/`deleteById`, raw
+`query()`, and the resource packages built on them — so all-or-nothing work
+needs no separate connection and no raw SQL:
+
+```ts
+await withTransaction(async () => {
+  const order = await create('orders', { userId, total })
+  await updateById('products', productId, { stock: stock - 1 })
+})
+```
+
+A nested `withTransaction()` joins the outer one. Calls made by unrelated
+concurrent requests do not join it.
+
+```typescript
+function withTransaction(fn: () => Promise<T>): Promise<T>
+```
+
+- `fn` — The work to run atomically.
+
+**Returns:** What `fn` resolves to.
+
 ## Available Providers
 
 | Provider      | Package                             |
 | ------------- | ----------------------------------- |
 | Cloudflare D1 | `@molecule/api-database-d1`         |
 | MySQL         | `@molecule/api-database-mysql`      |
+| PGlite        | `@molecule/api-database-pglite`     |
 | PostgreSQL    | `@molecule/api-database-postgresql` |
 | SQLite        | `@molecule/api-database-sqlite`     |
 
@@ -688,22 +727,17 @@ Data-access contract — the rules code generators most often get wrong:
   query lives on the pool/provider. The store also has NO `.exec()`,
   `.prepare()`, `.run()`, `.get()`, or `.all()` — those are driver methods
   (better-sqlite3 / pg) and calling them fails the type-check.
-- **Atomic multi-write = a MANUAL transaction on ONE connection; the store
-  helpers do NOT join it.** When several writes must be all-or-nothing (move
-  funds between two accounts, create an order AND decrement its stock, accept a
-  booking AND mark the slot taken), acquire a dedicated connection and drive
-  raw SQL on IT: `const conn = await connect()` then
-  `try { await conn.query('BEGIN'); …writes…; await conn.query('COMMIT') }`
-  `catch (e) { await conn.query('ROLLBACK').catch(() => {}); throw e }`
-  `finally { conn.release() }`. **The load-bearing gotcha:** the exported
-  `create`/`updateById`/`findMany`/`deleteById` run on the POOL's own
-  connection and commit INDEPENDENTLY — calling them between your `BEGIN` and
-  `COMMIT` does NOT enroll them in the transaction, so a mid-way failure leaves
-  those writes committed while the rest rolls back (a half-applied transfer).
-  Inside a transaction do every read AND write with `conn.query(sql, values)`
-  on that same `conn`, and ALWAYS `release()` in `finally` — a leaked
-  connection permanently drains the pool. Prefer this only for true multi-row
-  invariants; a single-row update is already atomic via `updateById`.
+- **Atomic multi-write = `withTransaction(async () => { … })`.** When several
+  writes must be all-or-nothing (move funds between two accounts, create an
+  order AND decrement its stock, accept a booking AND mark the slot taken),
+  wrap them: `await withTransaction(async () => { await create('orders', o);
+await updateById('products', id, { stock }) })`. Every call inside — the CRUD
+  helpers, `query()`, and the resource packages built on them — joins the one
+  transaction; it commits when the callback resolves and rolls back when it
+  throws. Never call `pool.transaction()` and then the CRUD helpers: those run
+  outside it (Postgres/MySQL: not atomic; SQLite: they wait behind it and fail
+  after 30 s). A single-row update is already atomic via `updateById`. D1 has
+  no interactive transactions, so `withTransaction` throws there.
 - **Create tables only via timestamped `.sql` files in `migrations/`** (the
   migration runner applies them on startup) — NEVER programmatically through
   the store. Seed rows with `create()`.

package/dist/index.d.ts

@@ -48,22 +48,17 @@
  *   query lives on the pool/provider. The store also has NO `.exec()`,
  *   `.prepare()`, `.run()`, `.get()`, or `.all()` — those are driver methods
  *   (better-sqlite3 / pg) and calling them fails the type-check.
- * - **Atomic multi-write = a MANUAL transaction on ONE connection; the store
- *   helpers do NOT join it.** When several writes must be all-or-nothing (move
- *   funds between two accounts, create an order AND decrement its stock, accept a
- *   booking AND mark the slot taken), acquire a dedicated connection and drive
- *   raw SQL on IT: `const conn = await connect()` then
- *   `try { await conn.query('BEGIN'); …writes…; await conn.query('COMMIT') }`
- *   `catch (e) { await conn.query('ROLLBACK').catch(() => {}); throw e }`
- *   `finally { conn.release() }`. **The load-bearing gotcha:** the exported
- *   `create`/`updateById`/`findMany`/`deleteById` run on the POOL's own
- *   connection and commit INDEPENDENTLY — calling them between your `BEGIN` and
- *   `COMMIT` does NOT enroll them in the transaction, so a mid-way failure leaves
- *   those writes committed while the rest rolls back (a half-applied transfer).
- *   Inside a transaction do every read AND write with `conn.query(sql, values)`
- *   on that same `conn`, and ALWAYS `release()` in `finally` — a leaked
- *   connection permanently drains the pool. Prefer this only for true multi-row
- *   invariants; a single-row update is already atomic via `updateById`.
+ * - **Atomic multi-write = `withTransaction(async () => { … })`.** When several
+ *   writes must be all-or-nothing (move funds between two accounts, create an
+ *   order AND decrement its stock, accept a booking AND mark the slot taken),
+ *   wrap them: `await withTransaction(async () => { await create('orders', o);
+ *   await updateById('products', id, { stock }) })`. Every call inside — the CRUD
+ *   helpers, `query()`, and the resource packages built on them — joins the one
+ *   transaction; it commits when the callback resolves and rolls back when it
+ *   throws. Never call `pool.transaction()` and then the CRUD helpers: those run
+ *   outside it (Postgres/MySQL: not atomic; SQLite: they wait behind it and fail
+ *   after 30 s). A single-row update is already atomic via `updateById`. D1 has
+ *   no interactive transactions, so `withTransaction` throws there.
  * - **Create tables only via timestamped `.sql` files in `migrations/`** (the
  *   migration runner applies them on startup) — NEVER programmatically through
  *   the store. Seed rows with `create()`.
@@ -90,4 +85,5 @@ export * from './types.js';
 export * from './provider.js';
 export * from './store.js';
 export * from './store-provider.js';
+export * from './transaction-context.js';
 //# sourceMappingURL=index.d.ts.map

package/dist/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAsFG;AAGH,cAAc,oBAAoB,CAAA;AAClC,cAAc,YAAY,CAAA;AAG1B,cAAc,eAAe,CAAA;AAG7B,cAAc,YAAY,CAAA;AAC1B,cAAc,qBAAqB,CAAA"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAiFG;AAGH,cAAc,oBAAoB,CAAA;AAClC,cAAc,YAAY,CAAA;AAG1B,cAAc,eAAe,CAAA;AAG7B,cAAc,YAAY,CAAA;AAC1B,cAAc,qBAAqB,CAAA;AACnC,cAAc,0BAA0B,CAAA"}

package/dist/index.js

@@ -48,22 +48,17 @@
  *   query lives on the pool/provider. The store also has NO `.exec()`,
  *   `.prepare()`, `.run()`, `.get()`, or `.all()` — those are driver methods
  *   (better-sqlite3 / pg) and calling them fails the type-check.
- * - **Atomic multi-write = a MANUAL transaction on ONE connection; the store
- *   helpers do NOT join it.** When several writes must be all-or-nothing (move
- *   funds between two accounts, create an order AND decrement its stock, accept a
- *   booking AND mark the slot taken), acquire a dedicated connection and drive
- *   raw SQL on IT: `const conn = await connect()` then
- *   `try { await conn.query('BEGIN'); …writes…; await conn.query('COMMIT') }`
- *   `catch (e) { await conn.query('ROLLBACK').catch(() => {}); throw e }`
- *   `finally { conn.release() }`. **The load-bearing gotcha:** the exported
- *   `create`/`updateById`/`findMany`/`deleteById` run on the POOL's own
- *   connection and commit INDEPENDENTLY — calling them between your `BEGIN` and
- *   `COMMIT` does NOT enroll them in the transaction, so a mid-way failure leaves
- *   those writes committed while the rest rolls back (a half-applied transfer).
- *   Inside a transaction do every read AND write with `conn.query(sql, values)`
- *   on that same `conn`, and ALWAYS `release()` in `finally` — a leaked
- *   connection permanently drains the pool. Prefer this only for true multi-row
- *   invariants; a single-row update is already atomic via `updateById`.
+ * - **Atomic multi-write = `withTransaction(async () => { … })`.** When several
+ *   writes must be all-or-nothing (move funds between two accounts, create an
+ *   order AND decrement its stock, accept a booking AND mark the slot taken),
+ *   wrap them: `await withTransaction(async () => { await create('orders', o);
+ *   await updateById('products', id, { stock }) })`. Every call inside — the CRUD
+ *   helpers, `query()`, and the resource packages built on them — joins the one
+ *   transaction; it commits when the callback resolves and rolls back when it
+ *   throws. Never call `pool.transaction()` and then the CRUD helpers: those run
+ *   outside it (Postgres/MySQL: not atomic; SQLite: they wait behind it and fail
+ *   after 30 s). A single-row update is already atomic via `updateById`. D1 has
+ *   no interactive transactions, so `withTransaction` throws there.
  * - **Create tables only via timestamped `.sql` files in `migrations/`** (the
  *   migration runner applies them on startup) — NEVER programmatically through
  *   the store. Seed rows with `create()`.
@@ -93,4 +88,5 @@ export * from './provider.js';
 // DataStore exports (abstract CRUD)
 export * from './store.js';
 export * from './store-provider.js';
+export * from './transaction-context.js';
 //# sourceMappingURL=index.js.map

package/dist/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAsFG;AAEH,eAAe;AACf,cAAc,oBAAoB,CAAA;AAClC,cAAc,YAAY,CAAA;AAE1B,sCAAsC;AACtC,cAAc,eAAe,CAAA;AAE7B,oCAAoC;AACpC,cAAc,YAAY,CAAA;AAC1B,cAAc,qBAAqB,CAAA"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAiFG;AAEH,eAAe;AACf,cAAc,oBAAoB,CAAA;AAClC,cAAc,YAAY,CAAA;AAE1B,sCAAsC;AACtC,cAAc,eAAe,CAAA;AAE7B,oCAAoC;AACpC,cAAc,YAAY,CAAA;AAC1B,cAAc,qBAAqB,CAAA;AACnC,cAAc,0BAA0B,CAAA"}

package/dist/transaction-context.d.ts

@@ -0,0 +1,46 @@
+/**
+ * `withTransaction(fn)`: every database call made while `fn` runs — the CRUD
+ * helpers (`create`, `findMany`, `updateById`, …) and `query()` alike — joins
+ * one transaction, on any bond that supports interactive transactions.
+ *
+ * Without it, the CRUD helpers run on the pool and commit on their own, so
+ * calling them between `BEGIN` and `COMMIT` is either quietly not atomic
+ * (Postgres, MySQL: a failure leaves half the writes committed) or a deadlock
+ * (SQLite: the open transaction holds the single connection, and the helper's
+ * query waits behind it forever).
+ *
+ * @module
+ */
+import type { DatabaseTransaction } from './types.js';
+/**
+ * The transaction opened by the enclosing `withTransaction()` call, if any.
+ * Bond pools call this from `query()` and send the statement to the active
+ * transaction when it is one they opened.
+ *
+ * @returns The active transaction, or `undefined` outside `withTransaction()`.
+ */
+export declare const getActiveTransaction: () => DatabaseTransaction | undefined;
+/**
+ * Runs `fn` inside one database transaction: commits when it resolves, rolls
+ * back and rethrows when it throws. Every database call made while `fn` runs
+ * joins the transaction — `create`/`findMany`/`updateById`/`deleteById`, raw
+ * `query()`, and the resource packages built on them — so all-or-nothing work
+ * needs no separate connection and no raw SQL:
+ *
+ * ```ts
+ * await withTransaction(async () => {
+ *   const order = await create('orders', { userId, total })
+ *   await updateById('products', productId, { stock: stock - 1 })
+ * })
+ * ```
+ *
+ * A nested `withTransaction()` joins the outer one. Calls made by unrelated
+ * concurrent requests do not join it.
+ *
+ * @param fn - The work to run atomically.
+ * @returns What `fn` resolves to.
+ * @throws {Error} If the bonded database has no interactive transactions
+ *   (Cloudflare D1), or rethrows what `fn` throws after rolling back.
+ */
+export declare const withTransaction: <T>(fn: () => Promise<T>) => Promise<T>;
+//# sourceMappingURL=transaction-context.d.ts.map

package/dist/transaction-context.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"transaction-context.d.ts","sourceRoot":"","sources":["../src/transaction-context.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAKH,OAAO,KAAK,EAAE,mBAAmB,EAAE,MAAM,YAAY,CAAA;AAgBrD;;;;;;GAMG;AACH,eAAO,MAAM,oBAAoB,QAAO,mBAAmB,GAAG,SAA+B,CAAA;AAE7F;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,eAAO,MAAM,eAAe,GAAU,CAAC,EAAE,IAAI,MAAM,OAAO,CAAC,CAAC,CAAC,KAAG,OAAO,CAAC,CAAC,CA4BxE,CAAA"}

package/dist/transaction-context.js

@@ -0,0 +1,82 @@
+/**
+ * `withTransaction(fn)`: every database call made while `fn` runs — the CRUD
+ * helpers (`create`, `findMany`, `updateById`, …) and `query()` alike — joins
+ * one transaction, on any bond that supports interactive transactions.
+ *
+ * Without it, the CRUD helpers run on the pool and commit on their own, so
+ * calling them between `BEGIN` and `COMMIT` is either quietly not atomic
+ * (Postgres, MySQL: a failure leaves half the writes committed) or a deadlock
+ * (SQLite: the open transaction holds the single connection, and the helper's
+ * query waits behind it forever).
+ *
+ * @module
+ */
+import { AsyncLocalStorage } from 'node:async_hooks';
+import { getPool } from './provider.js';
+const STORAGE_KEY = Symbol.for('@molecule/api-database/transaction-context');
+/**
+ * One storage per process, even if two copies of this package are installed:
+ * the bond and the application must see the same active transaction.
+ */
+const storage = (() => {
+    const holder = globalThis;
+    holder[STORAGE_KEY] ??= new AsyncLocalStorage();
+    return holder[STORAGE_KEY];
+})();
+/**
+ * The transaction opened by the enclosing `withTransaction()` call, if any.
+ * Bond pools call this from `query()` and send the statement to the active
+ * transaction when it is one they opened.
+ *
+ * @returns The active transaction, or `undefined` outside `withTransaction()`.
+ */
+export const getActiveTransaction = () => storage.getStore();
+/**
+ * Runs `fn` inside one database transaction: commits when it resolves, rolls
+ * back and rethrows when it throws. Every database call made while `fn` runs
+ * joins the transaction — `create`/`findMany`/`updateById`/`deleteById`, raw
+ * `query()`, and the resource packages built on them — so all-or-nothing work
+ * needs no separate connection and no raw SQL:
+ *
+ * ```ts
+ * await withTransaction(async () => {
+ *   const order = await create('orders', { userId, total })
+ *   await updateById('products', productId, { stock: stock - 1 })
+ * })
+ * ```
+ *
+ * A nested `withTransaction()` joins the outer one. Calls made by unrelated
+ * concurrent requests do not join it.
+ *
+ * @param fn - The work to run atomically.
+ * @returns What `fn` resolves to.
+ * @throws {Error} If the bonded database has no interactive transactions
+ *   (Cloudflare D1), or rethrows what `fn` throws after rolling back.
+ */
+export const withTransaction = async (fn) => {
+    if (storage.getStore())
+        return fn();
+    const pool = getPool();
+    if (!pool.transaction) {
+        throw new Error('withTransaction(): the bonded database has no interactive transactions (Cloudflare D1). Group the writes into one batch instead.');
+    }
+    const tx = await pool.transaction();
+    let result;
+    try {
+        result = await storage.run(tx, fn);
+    }
+    catch (error) {
+        try {
+            await tx.rollback();
+        }
+        catch (rollbackError) {
+            // Both failures matter: the work's error says why, the rollback's says the
+            // connection may still hold the transaction.
+            throw new AggregateError([error, rollbackError], 'withTransaction(): the work failed and so did the rollback', { cause: rollbackError });
+        }
+        throw error;
+    }
+    await tx.commit();
+    return result;
+};
+//# sourceMappingURL=transaction-context.js.map

package/dist/transaction-context.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"transaction-context.js","sourceRoot":"","sources":["../src/transaction-context.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAEH,OAAO,EAAE,iBAAiB,EAAE,MAAM,kBAAkB,CAAA;AAEpD,OAAO,EAAE,OAAO,EAAE,MAAM,eAAe,CAAA;AAGvC,MAAM,WAAW,GAAG,MAAM,CAAC,GAAG,CAAC,4CAA4C,CAAC,CAAA;AAE5E;;;GAGG;AACH,MAAM,OAAO,GAA2C,CAAC,GAAG,EAAE;IAC5D,MAAM,MAAM,GAAG,UAEd,CAAA;IACD,MAAM,CAAC,WAAW,CAAC,KAAK,IAAI,iBAAiB,EAAuB,CAAA;IACpE,OAAO,MAAM,CAAC,WAAW,CAAC,CAAA;AAC5B,CAAC,CAAC,EAAE,CAAA;AAEJ;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,oBAAoB,GAAG,GAAoC,EAAE,CAAC,OAAO,CAAC,QAAQ,EAAE,CAAA;AAE7F;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,MAAM,CAAC,MAAM,eAAe,GAAG,KAAK,EAAK,EAAoB,EAAc,EAAE;IAC3E,IAAI,OAAO,CAAC,QAAQ,EAAE;QAAE,OAAO,EAAE,EAAE,CAAA;IACnC,MAAM,IAAI,GAAG,OAAO,EAAE,CAAA;IACtB,IAAI,CAAC,IAAI,CAAC,WAAW,EAAE,CAAC;QACtB,MAAM,IAAI,KAAK,CACb,kIAAkI,CACnI,CAAA;IACH,CAAC;IACD,MAAM,EAAE,GAAG,MAAM,IAAI,CAAC,WAAW,EAAE,CAAA;IACnC,IAAI,MAAS,CAAA;IACb,IAAI,CAAC;QACH,MAAM,GAAG,MAAM,OAAO,CAAC,GAAG,CAAC,EAAE,EAAE,EAAE,CAAC,CAAA;IACpC,CAAC;IAAC,OAAO,KAAK,EAAE,CAAC;QACf,IAAI,CAAC;YACH,MAAM,EAAE,CAAC,QAAQ,EAAE,CAAA;QACrB,CAAC;QAAC,OAAO,aAAa,EAAE,CAAC;YACvB,2EAA2E;YAC3E,6CAA6C;YAC7C,MAAM,IAAI,cAAc,CACtB,CAAC,KAAK,EAAE,aAAa,CAAC,EACtB,4DAA4D,EAC5D,EAAE,KAAK,EAAE,aAAa,EAAE,CACzB,CAAA;QACH,CAAC;QACD,MAAM,KAAK,CAAA;IACb,CAAC;IACD,MAAM,EAAE,CAAC,MAAM,EAAE,CAAA;IACjB,OAAO,MAAM,CAAA;AACf,CAAC,CAAA"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@molecule/api-database",
-  "version": "1.0.2",
+  "version": "1.1.0",
   "description": "Database core interface for molecule.dev",
   "type": "module",
   "main": "dist/index.js",