Function createD1ExecutorDb

apps/host-cloudflare/src/db/d1.ts:87–154

(
  db: D1Database,
  blobs: R2Bucket | undefined,
)

// ---------------------------------------------------------------------------

export const createD1ExecutorDb = async (
  db: D1Database,
  blobs: R2Bucket | undefined,
): Promise<ExecutorDbHandle> => {
  const options = {
    tables: collectTables(),
    namespace: CLOUDFLARE_NAMESPACE,
    version: CLOUDFLARE_SCHEMA_VERSION,
    provider: "sqlite" as const,
  };

  const schema = createDrizzleRuntimeSchemaFromTables(options);
  const drizzleDb = drizzle(db, { schema });

  // D1 rejects SQL `BEGIN TRANSACTION` / `SAVEPOINT` (it requires the JS batch
  // API), and the shared ensure wraps its DDL in a transaction when the handle
  // exposes one. A generated fingerprint lets every Worker/DO isolate prove the
  // expected generated schema was already prepared with one primary read instead of
  // replaying dozens of idempotent CREATE/ALTER statements on every database
  // open. The marker is stored only after the ensure, data migrations, and any
  // required post-compatibility ensure succeed. Data migrations retain their
  // own ledger and still run below on every open.
  const expectedFingerprint = await schemaFingerprint(
    createDrizzleRuntimeSchemaSqlFromTables(options),
  );
  const preparedFingerprint = await readPreparedSchemaFingerprint(db);
  const requiresSchemaPreparation = preparedFingerprint !== expectedFingerprint;
  if (requiresSchemaPreparation) {
    await ensureDrizzleRuntimeSchemaFromTables({ run: (query) => drizzleDb.run(query) }, options);
  }
  const migrationResult = await prepareCloudflareD1Data(db, blobs);
  if (requiresSchemaPreparation) {
    // Compatibility migrations can rebuild a legacy table. Re-run the
    // idempotent ensure before stamping so the database matches the generated
    // schema after migration, including newer nullable columns the legacy
    // rebuild did not know about.
    if (migrationResult.schemaChanged) {
      await ensureDrizzleRuntimeSchemaFromTables({ run: (query) => drizzleDb.run(query) }, options);
    }
    await storePreparedSchemaFingerprint(db, expectedFingerprint);
  }

  // `interactiveTransactions: false` — D1 rejects interactive transactions, so
  // the fuma adapter runs transaction callbacks directly (auto-commit per
  // statement). Without this, every runtime write that wraps in a transaction
  // (adding a source, etc.) emits `BEGIN` and 500s. libSQL keeps real
  // transactions; D1 (same `provider: "sqlite"`) opts out here.
  const { db: fumaDb, fuma } = createExecutorFumaDb(drizzleDb, {
    ...options,
    interactiveTransactions: false,
    // D1 caps bound parameters at 100 per query; createMany batches to fit
    // (otherwise a wide table like `tool` overflows with "too many SQL
    // variables" when a source derives many tools).
    maxBoundParameters: 100,
  });

  return {
    db: fumaDb,