@blackglory/better-sqlite3-migrations

better-sqlite3-migrations

A utility for database migrations with better-sqlite3.

The module using user_version to record the schema version.

Install

npm install --save @blackglory/better-sqlite3-migrations
# or
yarn add @blackglory/better-sqlite3-migrations

API

interface IMigration {
  // An integer starting from 1
  version: number

  up: string | ((db: Database) => void)
  down: string | ((db: Database) => void)
}

You may need migration-files.

migrate

function migrate(
  db: Database
, migrations: IMigration[]
, options?: {
    targetVersion?: number
    throwOnNewerVersion?: boolean = false
  }
): void

If options.targetVersion is undefined, the maximum version of the migrations is used.

When the maximum known migration version is less than the user_version, it means the current instance is outdated.

• When options.throwOnNewerVersion is false (default), it will skip the migration, so your outdated instance continues to run.
• When options.throwOnNewerVersion is true, it will throw an error, so your outdated instance fails immediately.

Can multiple instances migrate in parallel?

Yes, the user_version update is visible to every database connection.

Each migration uses BEGIN IMMEDIATE to ensure that parallel write transactions fail early. Therefore, you may need a proper retry strategy.