- 3.Understand basic Sequelize setup and usage
- 4.Models tell our apps what data they can access; Migrations tell our databases how to be structured
- 1.A Model is an abstraction that represents a table within your database, in Sequelize the Model is a class, the instances of this class represent the data stored.
- 2.We will
Extend the Sequelize
Modelto define models at Rocket
- 3.We will use default table name inference for all Sequelize examples at Rocket, which automatically assumes table names are the pluralised form of model names
- 4.When passing in the second object that contains sequelize, we will pass two more key value pairs :
- 1.An instance of the Model class represents a row of data that is stored within the Sequelize database.
- 2.We will use the
createmethod to create model instances at Rocket instead of
- 3.Rocket recommends using the suggested way to log model instances with
- 4.Rocket recommends using
updateto update model instances for precision instead of
- 1.Model Querying allows developers to preform CRUD like actions to our database, we can preform actions such as create, read update and delete on the database
- 2.We will use
Model.create()to insert rows into our database instead of
- 3.We will rarely need to use syntax in "Advanced queries with functions (not just columns)" section, if ever
- 4.We will use
Model.bulkCreateto seed data in our databases for Rocket exercises
- 5.Limits and pagination will not be necessary until we have large amounts of data that slows down our apps when retrieved all at once
- 1.If you're not updating, inserting or deleting a value from your stored data, you're probably looking to list out some specific information, or even just all the data in your table, use the Model Query Finders to do this.
- 2.These are some of the most common Sequelize methods we will use in our apps
- 3.We can use the
Instance.findAll()method to select data from the database to use within our application
- 1.We will use migrations to set up our DB schema, the structure of our database, or the tables and their relationships. All companies use migrations to manage DB schema. Rocket considers migrations a core concept of Sequelize and ORMs in general.
- 2.Migrations at Rocket will only have "development" and "production" environments for simplicity. Tech teams in industry often have "test" environments for more robust testing between development and production.
- 3.We will use
model:generateat Rocket to generate model and migration files
- 4.Rocket will use seed files to populate initial date in our applications
- 5.Rocket will use
.sequelizercto specify Sequelize file and folder paths as per the example in "The
- 6.We will not use concepts from "Dynamic configuration" onward during Rocket's Bootcamp