drizzle-kit pull lets you literally pull(introspect) your existing database schema and generate schema.ts drizzle schema file,
it is designed to cover database first approach of Drizzle migrations.
How it works under the hood?
When you run Drizzle Kit pull command it will:
Pull database schema(DDL) from your existing database
Generate schema.ts drizzle schema file and save it to out folder
import * as p from "drizzle-orm/cockroach-core";export const users = p.cockroachTable("users", { id: p.int4().primaryKey(), name: p.string(), email: p.string(), }, (table) => [p.uniqueIndex('users_email_key').using('btree', table.email.asc())],);
It is a great approach if you need to manage database schema outside of your TypeScript project or
you’re using database, which is managed by somebody else.
drizzle-kit pull requires you to specify dialect and either
database connection url or user:password@host:port/db params, you can provide them
either via drizzle.config.ts config file or via CLI options:
You can have multiple config files in the project, it’s very useful when you have multiple database stages or multiple databases or different databases on the same project:
Drizzle Kit does not come with a pre-bundled database driver,
it will automatically pick available database driver from your current project based on the dialect - see discussion.
Initial pull
You can use the --init flag to mark the pulled schema as an applied migration in your database,
so that all subsequent migrations are diffed against the initial one
npx drizzle-kit pull --init
Including tables, schemas and extensions
drizzle-kit pull will by default manage all tables in all schemas.
You can configure list of tables, schemas and extensions via tablesFilters, schemaFilter and extensionFilters options.
tablesFilter
glob based table names filter, e.g. ["users", "user_info"] or "user*". Default is "*"
schemaFilter
glob based schema names filter, e.g. ["public", "drizzle"] or "drizzle*". Default is "*"
Let’s configure drizzle-kit to only operate with all tables in public schema
and let drizzle-kit know that there’s a postgis extension installed,
which creates it’s own tables in public schema, so drizzle can ignore them.
We recommend configuring drizzle-kit through drizzle.config.ts file,
yet you can provide all configuration options through CLI if necessary, e.g. in CI/CD pipelines, etc.
dialect
required
Database dialect, one of postgresqlmysqlsqlitetursosinglestoremssqlcockroach
driver
Drivers exceptions aws-data-apid1-httppglite
out
Migrations output folder path, default is ./drizzle
url
Database connection string
user
Database user
password
Database password
host
Host
port
Port
database
Database name
config
Configuration file path, default is drizzle.config.ts
introspect-casing
Strategy for JS keys creation in columns, tables, etc. preservecamel