import CodeTab from '@mdx/CodeTab.astro'; import CodeTabs from '@mdx/CodeTabs.astro'; import Section from '@mdx/Section.astro'; import Tab from '@mdx/Tab.astro'; import Tabs from '@mdx/Tabs.astro'; import Callout from '@mdx/Callout.astro'; import Npm from '@mdx/Npm.astro'; import Npx from '@mdx/Npx.astro'; import Steps from '@mdx/Steps.astro'; import Prerequisites from "@mdx/Prerequisites.astro"

Migrations with Drizzle Kit

<Prerequisites> - Get started with Drizzle and `drizzle-kit` - [read here](/docs/get-started) - Drizzle schema fundamentals - [read here](/docs/sql-schema-declaration) - Database connection basics - [read here](/docs/connect-overview) - Drizzle migrations fundamentals - [read here](/docs/migrations) </Prerequisites>

Drizzle Kit is a CLI tool for managing SQL database migrations with Drizzle. <Npm> -D drizzle-kit </Npm> <Callout type="warning"> Make sure to first go through Drizzle get started and migration fundamentals and pick SQL migration flow that suits your business needs best. </Callout>

Based on your schema, Drizzle Kit let's you generate and run SQL migration files, push schema directly to the database, pull schema from database, spin up drizzle studio and has a couple of utility commands. <Npx> drizzle-kit generate drizzle-kit migrate drizzle-kit push drizzle-kit pull drizzle-kit check drizzle-kit up drizzle-kit studio </Npx>


`drizzle-kit generate`	lets you generate SQL migration files based on your Drizzle schema either upon declaration or on subsequent changes, see here.
`drizzle-kit migrate`	lets you apply generated SQL migration files to your database, see here.
`drizzle-kit pull`	lets you pull(introspect) database schema, convert it to Drizzle schema and save it to your codebase, see here
`drizzle-kit push`	lets you push your Drizzle schema to database either upon declaration or on subsequent schema changes, see here
`drizzle-kit studio`	will connect to your database and spin up proxy server for Drizzle Studio which you can use for convenient database browsing, see here
`drizzle-kit check`	will walk through all generate migrations and check for any race conditions(collisions) of generated migrations, see here
`drizzle-kit up`	used to upgrade snapshots of previously generated migrations, see here

Drizzle Kit is configured through drizzle.config.ts configuration file or via CLI params.

It's required to at least provide SQL dialect and schema path for Drizzle Kit to know how to generate migrations.

📦 <project root>
 ├ 📂 drizzle
 ├ 📂 src
 ├ 📜 .env
 ├ 📜 drizzle.config.ts  <--- Drizzle config file
 ├ 📜 package.json
 └ 📜 tsconfig.json

import { defineConfig } from "drizzle-kit";

export default defineConfig({
  dialect: "postgresql",
  schema: "./src/schema.ts",
});

import { defineConfig } from "drizzle-kit";

export default defineConfig({
  out: "./drizzle",
  dialect: "postgresql",
  schema: "./src/schema.ts",

  driver: "pglite",
  dbCredentials: {
    url: "./database/",
  },

  extensionsFilters: ["postgis"],
  schemaFilter: "public",
  tablesFilter: "*",

  introspect: {
    casing: "camel",
  },

  migrations: {
    prefix: "timestamp",
    table: "__drizzle_migrations__",
    schema: "public",
  },

  breakpoints: true,
  strict: true,
  verbose: true,
});

</CodeTabs>

You can provide Drizzle Kit config path via CLI param, it's very useful when you have multiple database stages or multiple databases or different databases on the same project:

<Npx> drizzle-kit push --config=drizzle-dev.drizzle.config drizzle-kit push --config=drizzle-prod.drizzle.config </Npx> ```plaintext {5-6} 📦 <project root> ├ 📂 drizzle ├ 📂 src ├ 📜 .env ├ 📜 drizzle-dev.config.ts ├ 📜 drizzle-prod.config.ts ├ 📜 package.json └ 📜 tsconfig.json ```