SQL to Prisma Schema

What is SQL to Prisma?

SQL to Prisma reads one or more CREATE TABLE statements and generates a Prisma schema.prisma model block for each table — column types, primary keys, uniqueness, and defaults translated into Prisma's declarative field syntax.

How it works

The SQL is parsed into a structured table/column model (name, type, nullability, primary key, uniqueness, auto-increment, default expression, foreign key reference), then each column is mapped through a fixed type table — INTEGER/SERIAL → Int, VARCHAR/TEXT → String, TIMESTAMP → DateTime, UUID → String, and so on. A primary key becomes @id; SERIAL/AUTO_INCREMENT becomes @default(autoincrement()); a nullable, non-key column gets a trailing ?. Only a narrow, safe set of DEFAULT expressions is translated — numeric and string literals, booleans, and CURRENT_TIMESTAMP/NOW() (→ @default(now())). Anything else — a function call, an expression, a vendor-specific default — is emitted as a plain comment instead of a guessed Prisma attribute, and foreign keys are emitted as a comment noting the referenced table/column rather than a full @relation, since the relation's field name, array side, and cardinality aren't fully determined by the DDL alone.

Features

• Multiple CREATE TABLE statements in one paste, each becoming its own model
• snake_case columns renamed to camelCase Prisma fields
• Primary key, unique, and nullable modifiers mapped to @id, @unique, and ?
• Literal and now() defaults translated; anything else left as an honest comment
• Copy or download the generated .prisma file

Example

Input:

CREATE TABLE users (
  id SERIAL PRIMARY KEY,
  external_id UUID DEFAULT uuid_generate_v4(),
  name VARCHAR(255) NOT NULL,
  is_active BOOLEAN DEFAULT true
);

CREATE TABLE posts (
  id SERIAL PRIMARY KEY,
  user_id INTEGER NOT NULL REFERENCES users(id),
  title VARCHAR(255) NOT NULL,
  created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP
);

Output:

model User {
  id  Int  @id @default(autoincrement())
  externalId  String?  // SQL default not translated: uuid_generate_v4()
  name  String
  isActive  Boolean?  @default(true)
}

model Post {
  id  Int  @id @default(autoincrement())
  userId  Int  // FK -> users.id
  title  String
  createdAt  DateTime?  @default(now())
}

Common errors

An unmapped DEFAULT expression like uuid_generate_v4() never gets fabricated into a Prisma attribute — it's dropped in as // SQL default not translated: uuid_generate_v4() so you notice and add the equivalent (often @default(uuid()) or @default(dbgenerated("uuid_generate_v4()"))) by hand. Foreign key columns similarly surface only as // FK -> table.column comments — the schema won't compile as a real relational Prisma schema until you add the matching @relation fields on both models yourself. CHECK constraints, generated columns, and partitioning clauses in the source SQL aren't modeled at all and are silently skipped.

Best practices

Treat the output as a first draft: run prisma format and prisma validate after pasting it in, then search for the two comment markers (SQL default not translated and FK ->) to find every spot that needs manual attention before you can run prisma migrate or db push against it.