db-migrate/node-db-migrate

Is there a way to hook into an "afterMigrate" event?

Open

#384 opened on Jul 11, 2016

View on GitHub
 (6 comments) (1 reaction) (0 assignees)JavaScript (367 forks)batch import
documentationfeaturegood first issuehelp wanted

Repository metrics

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

Description

I'm trying to figure out a way to always run code after a migration happens, in my case I'm using mysql and I'd like to ensure a set of views is up to date so that we don't have to manually re-create our views after the underlying schema of the table changes. I noticed there is an endMigration event in the driver, maybe there is a way to hook into this?

Or perhaps if I put an index.js file in the migrations directory I can monkey patch the up function to call my recreate views methods after migrations are done?

Thanks for your help.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Contributor guide

Research direction
Explore the driver's endMigration event and propose a way to expose an afterMigrate hook that allows users to run custom code after each migration.
Tech stack
javascriptnodejsmysql
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
JavaScriptNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50