uql-orm 0.64.0 → 0.65.0

package/dist/sqlite/bunSqliteAdapter.bun.js

@@ -1,25 +0,0 @@
-/**
- * Presents a `bun:sqlite` handle as a {@link LocalSqliteDatabase}.
- *
- * @remarks Its statements expose no `reader`, so without deriving one every `RETURNING` statement
- * would take the `run()` path, which discards returned rows, and inserts would report no ids.
- * `columnNames` is non-empty for exactly the statements better-sqlite3 marks as readers.
- *
- * Lives in a `.bun.ts` file because it only ever executes under Bun: the Node coverage run cannot
- * reach it, and `sqliteQuerier.bun.test.ts` covers it under `test:bun` instead.
- */
-export function adaptBunSqlite(db) {
-    return {
-        prepare: (sql) => {
-            const stmt = db.prepare(sql);
-            return {
-                reader: stmt.columnNames.length > 0,
-                all: (...values) => stmt.all(...values),
-                run: (...values) => stmt.run(...values),
-                iterate: (...values) => stmt.iterate(...values),
-            };
-        },
-        loadExtension: (path) => db.loadExtension(path),
-        close: () => db.close(),
-    };
-}

package/dist/sqlite/nodeSqliteAdapter.d.ts

@@ -1,33 +0,0 @@
-import type { SqliteBindValue } from './abstractSqliteQuerier.js';
-import type { LocalSqliteDatabase } from './localSqliteQuerierPool.js';
-/**
- * A `node:sqlite` statement: better-sqlite3-shaped, except it describes columns instead of reporting
- * `reader`, and types `changes` as possibly `bigint` where better-sqlite3 always answers a `number`.
- */
-type NodeSqliteStatement = {
-    columns(): readonly unknown[];
-    all(...values: SqliteBindValue[]): unknown[];
-    run(...values: SqliteBindValue[]): {
-        changes: number | bigint;
-    };
-    iterate(...values: SqliteBindValue[]): Iterable<unknown>;
-};
-/**
- * Structural subset of `node:sqlite`'s `DatabaseSync`, declared locally for the same reason the rest
- * of this folder declares its driver shapes: nothing here depends on `@types/node` being in scope.
- */
-export type NodeSqliteDatabase = {
-    prepare(sql: string): NodeSqliteStatement;
-    loadExtension(path: string): void;
-    close(): void;
-};
-/**
- * Presents a `node:sqlite` handle as a {@link LocalSqliteDatabase}.
- *
- * @remarks Its statements expose no `reader`, so without deriving one every `RETURNING` statement
- * would take the `run()` path, which discards returned rows, and inserts would report no ids.
- * `columns()` is non-empty for exactly the statements better-sqlite3 marks as readers, including
- * `INSERT ... RETURNING` and `DELETE ... RETURNING`.
- */
-export declare function adaptNodeSqlite(db: NodeSqliteDatabase): LocalSqliteDatabase;
-export {};

package/dist/sqlite/nodeSqliteAdapter.js

@@ -1,25 +0,0 @@
-/**
- * Presents a `node:sqlite` handle as a {@link LocalSqliteDatabase}.
- *
- * @remarks Its statements expose no `reader`, so without deriving one every `RETURNING` statement
- * would take the `run()` path, which discards returned rows, and inserts would report no ids.
- * `columns()` is non-empty for exactly the statements better-sqlite3 marks as readers, including
- * `INSERT ... RETURNING` and `DELETE ... RETURNING`.
- */
-export function adaptNodeSqlite(db) {
-    return {
-        prepare: (sql) => {
-            const stmt = db.prepare(sql);
-            return {
-                reader: stmt.columns().length > 0,
-                all: (...values) => stmt.all(...values),
-                // `changes` is narrowed to `number` to match every other driver; a row count cannot exceed
-                // the safe-integer range, so nothing is lost.
-                run: (...values) => ({ changes: Number(stmt.run(...values).changes) }),
-                iterate: (...values) => stmt.iterate(...values),
-            };
-        },
-        loadExtension: (path) => db.loadExtension(path),
-        close: () => db.close(),
-    };
-}