Manual migrations

Summary

In this lesson, we explore manual migrations in Sails, where you take full responsibility for updating your database outside of Sails.

1. What are manual migrations?

   • You directly modify your database using SQL queries or MongoDB commands.

   • This applies to MongoDB, PostgreSQL, MySQL, or Microsoft SQL.

2. Why manual migrations?

   • Recommended for production to avoid unintended data loss or duplication.

   • Ensures full control over changes, such as:

     • Adding new columns

     • Creating new indexes

     • Updating data stores

3. Sails' approach

   • Sails provides flexibility, allowing you to handle migrations manually.

   • This is one of the two migration modes in Sails, with the next lesson covering the other approach.

Transcript

In this lesson, we’re looking at manual migrations, which involve updating your database outside of Sails.

What are manual migrations?

With this approach, you take full responsibility for updating your MongoDB, PostgreSQL, MySQL, or Microsoft SQL database manually.

• This means writing SQL queries or using MongoDB commands to apply changes.

• Any updates made to your Sails models must be manually reflected in the physical database.

Why manual migrations?

Manual migrations are strongly recommended for production because:

• Sails should not automatically migrate your database in a live environment.

• You’re handling sensitive data that must be carefully managed.

• It prevents accidental data loss or duplication.

Sails' approach to manual migrations

Sails allows you to opt out of automatic migrations and manage your database manually.

• You control schema changes, such as adding columns, creating indexes, or updating data stores.

• This is one of the two migration modes in Sails, with the next lesson covering the other method.