db-migrate/node-db-migrate

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

Open

#384 aberto em 11 de jul. de 2016

Ver no GitHub
 (6 comments) (1 reaction) (0 assignees)JavaScript (2.296 stars) (367 forks)batch import
documentationfeaturegood first issuehelp wanted

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.

Guia do colaborador

Pilha de tecnologia
javascriptnodejssqlmysql
Domain
backenddatabasedeveloper experience
Tipo Issue
feature
DifficultyDificuldade de implementação estimada para um novo contribuidor, de 1 para alterações muito pequenas a 5 para trabalho de nível especializado.
3
Tempo estimadoUm intervalo de tempo aproximado para um colaborador experiente investigar, implementar, testar e preparar um pull request.
1-2 days
Status da atividadeQuão disponível o issue aparece agora: novo, ativo, obsoleto, bloqueado ou aguardando entrada do mantenedor.
stale
ClarityCom que clareza o issue explica a mudança esperada, os critérios de aceitação e a próxima etapa.
mostly clear
Prerequisites
Knowledge of Node.jsFamiliarity with db migrate internalsUnderstanding of migration lifecycle
Simpatia para novatosUma pontuação de 1 a 100 que estima o quão acessível este issue é para colaboradores iniciantes.
30
Direção de pesquisa
Investigate the existing event system in db migrate, specifically the 'endMigration' event in the driver. Look at how other hooks are implemented and propose adding an 'afterMigrate' event that fires after each migration. Consider the API design and backward compatibility. The issue lacks concrete implementation details, so explore the codebase in the repo (e.g., lib/driver.js) and open a discussion on the relevant files.