Raulnq Node Hono React Monorepo Add DB Schema

Add / Modify Database Schema

Use this skill for any database schema changes: new tables, new columns, column modifications, or running migrations.

Step 0 — Read infrastructure files

Before making changes, read these files to understand the current DB setup:

• apps/backend/src/database/schemas.ts — re-export registry (see existing table exports)
• apps/backend/src/database/client.ts — Drizzle client setup
• apps/backend/drizzle.config.ts — migration config (check migrations.schema value)

The code templates below are the canonical patterns for table definitions — follow them exactly.

Decision tree

Creating a new table?

→ Go to Path A: New Table

Adding/modifying columns on an existing table?

→ Go to Path B: Modify Table

Just need to run migrations?

→ Go to Step: Run Migrations

Path A: New Table

A1. Create table definition

File: apps/backend/src/features/<entities>/<entity>.ts

import {
  varchar,
  pgSchema,
  uuid,
  boolean,
  numeric,
  integer,
  timestamp,
  date,
} from 'drizzle-orm/pg-core';

const dbSchema = pgSchema('<schema>');

export const <entities> = dbSchema.table('<entities>', {
  <entityId>: uuid('<entityId>').primaryKey(),
  name: varchar('name', { length: 1024 }).notNull(),
  price: numeric('price', {
    precision: 10,
    scale: 2,
    mode: 'number'
  }).notNull(),
  quantity: integer('quantity').notNull(),
  createdAt: timestamp('createdAt', {
    mode: 'date',
    withTimezone: true
  }).notNull().defaultNow(),
  // ... other columns
});

Key rules:

• pgSchema('<schema>') — The schema is the same in migrations.schema(apps/backend/drizzle.config.ts). Do NOT use pgTable() (which defaults to public schema).
• UUID primary key: uuid('<entityId>').primaryKey() — no .defaultRandom()
• varchar with explicit length: always specify { length: N }
• numeric with mode: 'number': always specify { precision, scale, mode: 'number' } to get TypeScript number type
• timestamp with mode: 'date': always specify { mode: 'date', withTimezone: true } to get JavaScript Date objects
• .notNull() on all required columns
• Column name in quotes must match the property name exactly

A2. Re-export from schema registry

File: apps/backend/src/database/schemas.ts

Add:

export { <entities> } from '#/features/<entities>/<entity>.js';

This is required — Drizzle Kit reads schemas.ts to discover all tables for migration generation.

A3. Create Zod schemas

File: apps/backend/src/features/<entities>/schemas.ts

Zod schemas must stay in sync with the Drizzle table:

import { paginationSchema } from '#/pagination.js';
import { z } from 'zod';

export const <entity>Schema = z.object({
  <entityId>: z.uuidv7(),
  name: z.string().min(1).max(1024),
  // mirror every column
});

export type <Entity> = z.infer<typeof <entity>Schema>;

// Add, Edit, List schemas derived from base...

A4. Run migrations

See Step: Run Migrations below.

Path B: Modify Table

B1. Edit the table definition

Modify the existing file in apps/backend/src/features/<entities>/<entity>.ts:

• Adding a column: add the new property to the table object
• Changing a column: update the type/constraints
• Removing a column: remove the property

B2. Update Zod schemas

File: apps/backend/src/features/<entities>/schemas.ts

Keep Zod schemas in sync with the Drizzle table. Update:

• Base entity schema (add/remove/modify field)
• Add schema (if new field should be in creation payload)
• Edit schema (if new field should be editable)
• List schema (if new field should be a filter)

B3. Update endpoints if needed

If a new column needs to be handled in endpoints (e.g., set defaults in add, include in edit), update the relevant endpoint files.

B4. Run migrations

See Step: Run Migrations below.

Step: Run Migrations

Generate migration

npm run database:generate -w @node-monorepo/backend

This runs drizzle-kit generate which reads drizzle.config.ts → schemas.ts → all table definitions and produces SQL migration files in apps/backend/src/database/migrations/.

Apply migration

npm run database:migrate -w @node-monorepo/backend

This runs drizzle-kit migrate which applies pending migrations to the database.

Verify with Drizzle Studio (optional)

npm run database:studio -w @node-monorepo/backend

Column type quick reference

import {
  varchar,
  uuid,
  boolean,
  integer,
  numeric,
  doublePrecision,
  timestamp,
  date,
  text,
  pgSchema,
} from 'drizzle-orm/pg-core';

// Common column patterns:
uuid('columnId').primaryKey(); // UUID primary key
varchar('name', { length: 1024 }).notNull(); // Required string
varchar('description', { length: 4096 }); // Optional string
boolean('active').notNull(); // Required boolean
integer('quantity').notNull(); // Required integer
text('content').notNull(); // Unlimited text (notes, descriptions)
varchar('status', { length: 25 }).notNull(); // Status/state fields

// Foreign key reference
uuid('relatedId')
  .notNull()
  .references(() => relatedTable.relatedId); // FK with constraint

// Numeric columns (prices, measurements, etc.)
numeric('price', {
  precision: 10,
  scale: 2,
  mode: 'number',
}).notNull(); // Required decimal (returns as number)

numeric('amount', {
  precision: 10,
  scale: 2,
  mode: 'number',
}); // Optional decimal

// Geographic coordinates
doublePrecision('latitude'); // Returns as number by default
doublePrecision('longitude');

// Timestamp columns (created/updated tracking)
timestamp('createdAt', {
  mode: 'date',
  withTimezone: true,
})
  .notNull()
  .defaultNow(); // Auto-generated, returns Date object

timestamp('updatedAt', {
  mode: 'date',
  withTimezone: true,
}); // Optional, returns Date object

// Date-only columns (birthdate, deadline, etc.)
date('birthDate', {
  mode: 'string',
}); // Returns 'YYYY-MM-DD' string (avoids timezone issues)

date('deadline', {
  mode: 'string',
}).notNull(); // Required date, returns 'YYYY-MM-DD'

Important:

• Numeric columns: Always use mode: 'number' for numeric() to get TypeScript number types instead of strings.
• Timestamp columns: Always use mode: 'date' with withTimezone: true to get JavaScript Date objects with timezone information.
• Date-only columns: Use date() with mode: 'string' to get 'YYYY-MM-DD' strings. This avoids timezone shift bugs that occur when using Date objects for date-only values.
• Auto timestamps: Use .defaultNow() for auto-generated creation timestamps.
• Coordinates: Use doublePrecision() for latitude/longitude (returns number by default).
• Foreign keys: Use .references(() => relatedTable.relatedId) — import the related table from its feature. The arrow function syntax avoids circular dependency issues.

Checklist

• Table definition created/updated in feature directory
• Re-exported from apps/backend/src/database/schemas.ts
• drizzle.config.ts updated if new schema name
• Zod schemas updated to match table changes
• Endpoints updated if column affects request/response
• Migration generated: npm run database:generate -w @node-monorepo/backend
• Migration applied: npm run database:migrate -w @node-monorepo/backend

Critical rules

• pgSchema('...') — never pgTable() (avoids public schema)
• No .defaultRandom() on UUIDs — app generates UUIDv7 via v7() from uuid
• .js extension on all imports
• Re-export required in database/schemas.ts for Drizzle Kit discovery
• Zod schemas must stay in sync with Drizzle table after every change

Converted and distributed by TomeVault — claim your Tome and manage your conversions.