Schema.rb understanding in Ruby on Rails - Step-by-Step Execution

Concept Flow - Schema.rb understanding

Run migration

↓

Update database structure

↓

Rails generates schema.rb

↓

schema.rb reflects current DB schema

↓

Use schema.rb to recreate DB structure

This flow shows how running migrations updates the database and then Rails creates schema.rb to represent the current database structure.

Execution Sample

Ruby on Rails

create_table :users do |t|
  t.string :name
  t.integer :age
end

This migration creates a users table with name and age columns.

Execution Table

Step	Action	Effect on DB	Effect on schema.rb
1	Run migration file	Creates users table with columns name:string, age:integer	schema.rb unchanged
2	Rails writes schema.rb	No change to DB	schema.rb now matches DB structure
3	Use schema.rb to setup DB	Creates users table with same columns	schema.rb unchanged
4	No migration changes	DB unchanged	schema.rb unchanged

💡 schema.rb matches the current database schema after migrations run

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
Database tables	empty	users table created	users table created	users table created	users table created
schema.rb content	empty	empty	users table with name:string, age:integer	users table with name:string, age:integer	users table with name:string, age:integer

Key Moments - 2 Insights

Why does schema.rb update only after running migrations?

Because schema.rb is generated by Rails to reflect the current database structure after migrations have changed it, as shown in execution_table step 2.

Can schema.rb be used to create the database without running migrations?

Yes, schema.rb can be loaded to recreate the database structure directly, as shown in execution_table step 3.

Visual Quiz - 3 Questions

Look at the execution table, what happens to schema.rb after running the migration?

A It deletes the users table

B It remains empty

C It updates to reflect the new database structure

D It changes the migration file

💡 Hint

See execution_table row 1 and 2 for schema.rb changes

At which step does schema.rb get used to recreate the database?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Check execution_table row 3 describing schema.rb usage

If no migrations run, what happens to the database and schema.rb?

A Database unchanged, schema.rb unchanged

B Database changes, schema.rb unchanged

C Both change

D schema.rb changes, database unchanged

💡 Hint

Look at execution_table row 4 for no changes

Concept Snapshot

schema.rb is a Ruby file that shows the current database structure.
It is updated automatically after running migrations.
You can use schema.rb to recreate the database schema without running migrations.
It helps keep your database structure consistent and shareable.
Always run migrations first to keep schema.rb accurate.

Full Transcript

In Rails, when you run migrations, the database structure changes. After migrations finish, Rails generates a file called schema.rb. This file shows the current state of your database tables and columns in Ruby code. You can use schema.rb to recreate your database structure without running migrations. This helps keep your database consistent across different environments. If you don't run migrations, schema.rb and the database stay the same. Remember, schema.rb is a snapshot of your database schema after migrations run.