@nextlyhq/adapter-drizzle 0.0.2-alpha.46 → 0.0.2-alpha.48

package/dist/{adapter-CbGoHa-2.d.cts → adapter-Ch_5ecmp.d.cts}

@@ -1,6 +1,6 @@
-import { AnyRelations } from 'drizzle-orm';
+import { AnyRelations, SQL } from 'drizzle-orm';
 import { S as SupportedDialect, a as SqlParam, T as TableResolver } from './core-CVO7WYDj.cjs';
-import { T as TransactionContext, e as TransactionOptions, D as DatabaseCapabilities, P as PoolStats, S as SelectOptions, I as InsertOptions, W as WhereClause, U as UpdateOptions, f as DeleteOptions, g as UpsertOptions, a as Migration, d as MigrationResult } from './migration-B41DME-y.cjs';
+import { T as TransactionContext, e as TransactionOptions, D as DatabaseCapabilities, P as PoolStats, S as SelectOptions, I as InsertOptions, W as WhereClause, U as UpdateOptions, f as DeleteOptions, g as UpsertOptions, a as Migration, d as MigrationResult } from './migration-BUc56kip.cjs';
 import { T as TableDefinition, C as CreateTableOptions, D as DropTableOptions, A as AlterTableOperation, a as AlterTableOptions } from './schema-BDn8WfSL.cjs';
 import { D as DatabaseErrorKind, a as DatabaseError } from './error-um1d_3Uo.cjs';
 
@@ -122,6 +122,27 @@ declare abstract class DrizzleAdapter {
      * Returns null if no resolver is set or table is not found.
      */
     protected getTableObject(tableName: string): unknown;
+    /**
+     * Run a Drizzle-built statement and return its rows.
+     *
+     * @remarks
+     * The CRUD methods resolve their table through the schema registry and reject
+     * any name it does not declare, which leaves no way to read from a table the
+     * ORM does not know — one mid-rename, above all — except by assembling SQL and
+     * quoting identifiers by hand. This takes Drizzle's `sql` template instead, so
+     * the dialect in use decides the quoting and the parameter binding.
+     *
+     * Concrete rather than abstract so existing adapters keep working unchanged.
+     * The three drivers disagree about both the call and the result: node-postgres
+     * returns `{ rows }`, mysql2 a `[rows, fields]` tuple, and better-sqlite3 has
+     * no `execute` at all and answers `all`. Keeping that here rather than at each
+     * call site is the point — a caller reasoning about it would be reasoning
+     * about a driver it cannot see.
+     *
+     * @param statement - Drizzle `sql` template to run
+     * @returns Rows the statement produced
+     */
+    queryStatement<T = Record<string, unknown>>(statement: SQL): Promise<T[]>;
     /**
      * Map data keys from SQL column names (snake_case) to Drizzle JS property names (camelCase).
      * Drizzle schemas define columns as e.g. `createdAt: timestamp("created_at")` — the JS

package/dist/{adapter-D1vI8njz.d.ts → adapter-DJtzp_R8.d.ts}

@@ -1,6 +1,6 @@
-import { AnyRelations } from 'drizzle-orm';
+import { AnyRelations, SQL } from 'drizzle-orm';
 import { S as SupportedDialect, a as SqlParam, T as TableResolver } from './core-CVO7WYDj.js';
-import { T as TransactionContext, e as TransactionOptions, D as DatabaseCapabilities, P as PoolStats, S as SelectOptions, I as InsertOptions, W as WhereClause, U as UpdateOptions, f as DeleteOptions, g as UpsertOptions, a as Migration, d as MigrationResult } from './migration-XV8CXMZT.js';
+import { T as TransactionContext, e as TransactionOptions, D as DatabaseCapabilities, P as PoolStats, S as SelectOptions, I as InsertOptions, W as WhereClause, U as UpdateOptions, f as DeleteOptions, g as UpsertOptions, a as Migration, d as MigrationResult } from './migration-Bj84e15B.js';
 import { T as TableDefinition, C as CreateTableOptions, D as DropTableOptions, A as AlterTableOperation, a as AlterTableOptions } from './schema-BIQ0YQZ_.js';
 import { D as DatabaseErrorKind, a as DatabaseError } from './error-um1d_3Uo.js';
 
@@ -122,6 +122,27 @@ declare abstract class DrizzleAdapter {
      * Returns null if no resolver is set or table is not found.
      */
     protected getTableObject(tableName: string): unknown;
+    /**
+     * Run a Drizzle-built statement and return its rows.
+     *
+     * @remarks
+     * The CRUD methods resolve their table through the schema registry and reject
+     * any name it does not declare, which leaves no way to read from a table the
+     * ORM does not know — one mid-rename, above all — except by assembling SQL and
+     * quoting identifiers by hand. This takes Drizzle's `sql` template instead, so
+     * the dialect in use decides the quoting and the parameter binding.
+     *
+     * Concrete rather than abstract so existing adapters keep working unchanged.
+     * The three drivers disagree about both the call and the result: node-postgres
+     * returns `{ rows }`, mysql2 a `[rows, fields]` tuple, and better-sqlite3 has
+     * no `execute` at all and answers `all`. Keeping that here rather than at each
+     * call site is the point — a caller reasoning about it would be reasoning
+     * about a driver it cannot see.
+     *
+     * @param statement - Drizzle `sql` template to run
+     * @returns Rows the statement produced
+     */
+    queryStatement<T = Record<string, unknown>>(statement: SQL): Promise<T[]>;
     /**
      * Map data keys from SQL column names (snake_case) to Drizzle JS property names (camelCase).
      * Drizzle schemas define columns as e.g. `createdAt: timestamp("created_at")` — the JS

package/dist/index.cjs

@@ -151,6 +151,45 @@ var DrizzleAdapter = class {
   getTableObject(tableName) {
     return this.tableResolver?.getTable(tableName) ?? null;
   }
+  /**
+   * Run a Drizzle-built statement and return its rows.
+   *
+   * @remarks
+   * The CRUD methods resolve their table through the schema registry and reject
+   * any name it does not declare, which leaves no way to read from a table the
+   * ORM does not know — one mid-rename, above all — except by assembling SQL and
+   * quoting identifiers by hand. This takes Drizzle's `sql` template instead, so
+   * the dialect in use decides the quoting and the parameter binding.
+   *
+   * Concrete rather than abstract so existing adapters keep working unchanged.
+   * The three drivers disagree about both the call and the result: node-postgres
+   * returns `{ rows }`, mysql2 a `[rows, fields]` tuple, and better-sqlite3 has
+   * no `execute` at all and answers `all`. Keeping that here rather than at each
+   * call site is the point — a caller reasoning about it would be reasoning
+   * about a driver it cannot see.
+   *
+   * @param statement - Drizzle `sql` template to run
+   * @returns Rows the statement produced
+   */
+  async queryStatement(statement) {
+    if (this.getCapabilities().dialect === "sqlite") {
+      const db2 = this.getDrizzle();
+      return await db2.all(statement);
+    }
+    const db = this.getDrizzle();
+    const result = await db.execute(statement);
+    if (Array.isArray(result)) {
+      return Array.isArray(result[0]) ? result[0] : result;
+    }
+    if (typeof result === "object" && result !== null && Array.isArray(result.rows)) {
+      return result.rows;
+    }
+    throw this.createDatabaseError(
+      "query",
+      "Drizzle statement returned a result shape this adapter does not recognise; refusing to report it as an empty result.",
+      void 0
+    );
+  }
   /**
    * Map data keys from SQL column names (snake_case) to Drizzle JS property names (camelCase).
    * Drizzle schemas define columns as e.g. `createdAt: timestamp("created_at")` — the JS