db-migrate/node-db-migrate

Feature Request: Transaction configuration on a per migration basis

Open

#659 opened on Dec 11, 2019

View on GitHub
 (5 comments) (3 reactions) (1 assignee)JavaScript (367 forks)batch import
featuregood first issuehelp wanted

Repository metrics

Stars
 (2,296 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

I'm submitting a...

  • Bug report
  • Feature request
  • Question

Current behavior

There is no way to turn off transactions for individual migrations.

Expected behavior

Certain migrations need to be run outside of a transaction. For example, in PostgreSQL, ALTER TYPE type_name ADD new_value cannot be run in a transaction. The rest of the migrations, however should be run in a transaction. There is currently no way to configure individual migrations to not use a transaction block. It would be extremely helpful to allow this to be part of the configuration for a single migration.

Contributor guide

Research direction
Explore how migrations are currently handled; consider adding a `transaction` option to migration configurations or a method like `withoutTransaction()`.
Tech stack
javascriptnodejs
Domain
databasebackend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Node.jsSQL
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70