ormDB + Prisma

What This Adapter Does

ormDB is a relational database engine written in Rust that replaces PostgreSQL, MySQL, and SQLite as the actual database underneath your application. The @ormdb/prisma-adapter package connects Prisma’s query engine to ormDB, so you keep your existing Prisma schema, models, and application code while gaining ormDB’s native graph-fetch queries, zero-copy wire protocol, and built-in capabilities like vector search and change streams.

Prisma already thinks in terms of object graphs. When you write findMany with nested include blocks, Prisma understands you want related data. The problem is that traditional SQL databases force Prisma to decompose that intent into multiple sequential queries, creating the N+1 problem. ormDB understands the graph natively, resolving your entire include tree in a single round-trip via graph-fetch queries.

Quick Setup

Install the adapter alongside your existing Prisma setup:

npm install @ormdb/prisma-adapter

Update your Prisma schema datasource:

datasource db {
  provider = "ormdb"
  url      = env("ORMDB_URL")
}

Initialize the adapter in your application:

import { PrismaClient } from '@prisma/client'
import { withOrmDB } from '@ormdb/prisma-adapter'

const prisma = withOrmDB(new PrismaClient())

// Your existing queries work unchanged
const users = await prisma.user.findMany({
  include: {
    posts: {
      include: {
        comments: true,
        tags: true,
      },
    },
  },
})

What Changes, What Stays the Same

Stays the same: Your Prisma schema, model definitions, relation declarations, all findMany/findUnique/create/update/delete operations, and nested include/select queries.

Changes: The database underneath. Instead of PostgreSQL issuing multiple SQL queries to resolve nested includes, ormDB fetches the entire object graph in one round-trip. Migrations gain A-D safety grading. You get built-in vector search, geo search, full-text search, and change streams without extensions.

Removed: Raw SQL queries ($queryRaw, $executeRaw) are not available because ormDB does not speak SQL. If your application relies on raw SQL, those specific calls need to be refactored into Prisma’s type-safe query API. See best database for Prisma users for a deeper comparison of database options for Prisma.