Database Migration Management Framework

From @kjdelisle on July 28, 2017 18:37

Scenario

FooCorp wants to deploy version 2.0 of their LoopBack application on their production server, but doing so will require some alteration of the schema in their database. Some of these changes require a more delicate touch that cannot necessarily be performed by the autoupdate function.

Currently, FooCorp would have to create their own scripts and execute them to modify their database schema to match their expectations, which may require them to more directly interface with drivers that are used by their chosen LoopBack connector, or using another implementation entirely!

Proposal

Create a component for use in loopback-next that handles the idea of production-system migration within a LoopBack application as it is upgraded from one release to another.

Originally, I had a design in my mind for how this would work, but I noticed that there are some generic migration tools on npm (https://www.npmjs.com/package/migration), and I was wondering if there was anything additional that we'd want to add to make it easier to do this sort of thing.

Martin Fowler's Evolutionary Database Design provides a comprehensive information on this topic, including implementation examples.

Other ORM frameworks have been supporting migrations for quite some time, we can inspire from them.

• Migrations in Ruby on Rails
• .NET EntityFramework's Code First Migrations

La proposition ne mentionne aucun fichier du dépôt, test ou point d’entrée. Commencez par examiner l’idée du package de migration et les exemples référencés d’Evolutionary Database Design et de migrations ORM ; le travail serait considéré comme terminé lorsqu’une conception de migration de production approuvée et son implémentation dans loopback-next seraient disponibles.