Sequelize Migration 

This is an oldie, but it sure helped me a ton just now! Migrations sounded like a big and scary word, but really with Sequelize and a little bit of knowledge it's really quite easy to do without fear of deleting my data. Thanks Ben

It's like every issue I face you have a video to cover it, you are the best teacher ever!

Thank you. this have been so much help to me!

13.5 add "async" before the parenthesis : async (queryInterface, Sequelize) => {}

Thanks, really helpful tutorials

Thank you, Ben.

Thank you brother 💓

It was helpful!

That's how your safe config.JS has to look like for migration: p.s CLI works with .js files and .json. To work with env.vars you have to use .js. Also note - we have to npm install dotenv package require('dotenv').config(); module.exports = { dev: { username: process.env.DB_USER, password: process.env.DB_PASS, database: process.env.DB_NAME, host: process.env.DB_HOST, dialect: 'mysql' }, "production": { "username": process.env.DB_USER, "password": process.env.DB_PASS, "database": process.env.DB_NAME, "host": process.env.DB_HOST, "dialect": "mysql" } }

I was confused why we need migration and how to use it. after watching this video, Thankfully I am even more confused :D

What is the command interpreter environment you are running this in?

Thanks

New drinking game: take a shot everytime you here an american say "actually" in an online tutorial video. Dont die.

sequelize db:migrate:undo 💁

In a migration, is it possible to update a column based on a column in another table? I want to use bulkUpdate to updated with a join condition but am unsure how

Am I correct in thinking that if you have auto-save setup on your editor, and are running the app via "yarn start", then you could make a mess of what you are trying to achieve. The database will be re-tooled via the sync command and will get rid of all that data before you have the chance to run the migration - and the migration will also fail. 2 options 1) Always make sure you are not running your app while doing migrations (too much room for error) 2) disable the sync in the index.js and rely soley on implementing migrations for db changes as a best practice re #2, would I just remove the first line from the following and just start from server.listen()? I am referring to this statement in index.js models.sequelize.sync({ force: false }).then(() => { server.listen(PORT, () => { new SubscriptionServer( ... ...

How do i implement associations when using migrations?

Why is necessary to use sequelize migrations?

Hey what terminal is that?

Have you uploaded this code your github repository?