Why models represent data in Ruby on Rails - Visual Breakdown

Concept Flow - Why models represent data

User interacts with app

↓

Controller receives request

↓

Controller asks Model for data

↓

Model talks to Database

↓

Database returns data to Model

↓

Model sends data to Controller

↓

Controller sends data to View

↓

View shows data to User

This flow shows how models act as the middleman between the database and the app, holding and managing data.

Execution Sample

Ruby on Rails

class User < ApplicationRecord
end

user = User.find(1)
puts user.name

This code fetches a user record from the database and prints the user's name.

Execution Table

Step	Action	Model State	Database Interaction	Output
1	Call User.find(1)	No user loaded	Query database for user with id=1	No output yet
2	Database returns user data	User object created with id=1, name='Alice'	Data fetched	No output yet
3	Access user.name	User object with name='Alice'	No database call	Returns 'Alice'
4	puts user.name	User object unchanged	No database call	Prints 'Alice' to console
5	End of code	User object exists	No database call	Execution stops

💡 Code ends after printing the user's name

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
user	nil	nil	User(id=1, name='Alice')	User(id=1, name='Alice')	User(id=1, name='Alice')

Key Moments - 3 Insights

Why does calling User.find(1) not immediately print anything?

Because User.find(1) only fetches data and creates a model object; printing happens only when puts user.name is called (see execution_table step 4).

Is the model the same as the database?

No, the model is a Ruby object that holds data from the database and adds behavior; the database stores the raw data (see execution_table steps 1 and 2).

Why do we use models instead of talking directly to the database?

Models organize data and logic in one place, making code cleaner and easier to maintain (see concept_flow).

Visual Quiz - 3 Questions

Look at the execution_table, what is the state of 'user' after step 2?

A User object with id=1 and name='Alice'

B nil

C User object with no data

D String 'Alice'

💡 Hint

Check the 'Model State' column in execution_table row for step 2

At which step does the database return data to the model?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the 'Database Interaction' column in execution_table

If we change 'puts user.name' to 'puts user.id', what output will change?

A Output will be 'Alice' still

B Output will be '1' instead of 'Alice'

C No output will be printed

D Code will error

💡 Hint

Refer to the 'Output' column in execution_table step 4 and variable_tracker for user attributes

Concept Snapshot

Models in Rails represent data from the database.
They act as Ruby objects holding data and behavior.
Use Model.find(id) to get data as objects.
Models keep app code clean and organized.
They separate data logic from views and controllers.

Full Transcript

In Rails, models represent data by acting as Ruby objects that connect to the database. When the app needs data, the controller asks the model, which queries the database and returns data wrapped in an object. This object holds the data and can have methods to work with it. For example, calling User.find(1) fetches the user with id 1 from the database and creates a User object. Accessing user.name gets the name attribute from that object. Models help keep data logic separate from the user interface and controller code, making the app easier to build and maintain.