I have tried others too, but some of them are not well-maintained anymore, and I faced issues getting set up with others. There are quite a few npm modules available already, but I have used the library node-migrate. So you need to query all the documents where this member doesn’t exist and update them. When a member has been added to the schema, existing document won’t have the info. Since this article is about automating migrations, I am going to show you how you can write a simple script that will take care of schema changes as well as unit tests. I personally see this as overhead to maintaining code and it becomes inflexible. If the code is somehow removed, then many of documents are not upgradeable.įor instance, if there have been 3 versions of a document, and we remove the upgrade code from version 1 to version 2, any documents that still exist as version 1 are not upgradeable. The second one is much more code-dependent and must stay in your codebase. Write a script that will take care of upgrading the schema as well as downgrading it to previous versions.So how do you handle all of the above changes? The representation of a member is changed.

There are a number of different ways that a schema can change from one version of your application to the next. And we have to make sure data remains consistent throughout the application. As a software developer at some point, you might have to deal with database migrations in one way or another.Īs software or applications evolve and improve over the time, your database must as well.

Npoco idatabase updateasync