Schema

Create new table

Create src/db/schema/note.ts. Import user from the auth file to use it for relations:

import { sqliteTable, text } from "drizzle-orm/sqlite-core";

import { user } from "./auth";

export const note = sqliteTable("note", {
  id: text("id").primaryKey(),
  userId: text("user_id")
    .notNull()
    .references(() => user.id, { onDelete: "cascade" }),
  title: text("title").notNull(),
});

The foreign key ties notes to individual users. Cascading deletion removes their notes when the auth user is deleted. Choose the deletion policy deliberately for your own data, especially records that need to survive account deletion.

Export it

Add the new file to src/db/schema/index.ts:

export * from "./auth";
export * from "./note";

src/db/index.ts and src/db/script.ts already pass this barrel to Drizzle. drizzle.config.ts points Drizzle Kit at src/db/schema/index.ts, so the same export is what migration generation sees. After it, import { note } from "@/db/schema" works in server code, and db.query.note is available.

Do not rename the existing Better Auth tables or change the adapter's provider: "sqlite". If you extend a Better Auth user field, declare it in the auth configuration so the generator includes it in auth.ts. See Better Auth schema extensions.

Generate and inspect the migration

For an application-only table change, generate SQL from the existing schema without rerunning auth generation:

pnpm exec drizzle-kit generate

When auth configuration or plugins change, use the combined script:

pnpm db:generate

Both paths write migrations to drizzle/. Review the SQL before applying it. A new note table should create that table and its foreign key. Unexpected drops of auth or application tables mean a schema file is missing from the barrel.

pnpm db:migrate --local

Check the new table locally:

pnpm wrangler d1 execute DB --local --command "PRAGMA table_info('note');"

Once the local path works, follow migration deployment. For a full UI-to-database implementation, use add a feature.