Column types and attributes in Ruby on Rails - Step-by-Step Execution

Concept Flow - Column types and attributes

Define Migration

↓

Choose Table Name

↓

Add Column with Type

↓

Set Attributes (null, default, limit)

↓

Run Migration

↓

Database Table Updated

This flow shows how a Rails migration defines a table column with a type and attributes, then updates the database.

Execution Sample

Ruby on Rails

create_table :users do |t|
  t.string :name, null: false, default: "Guest"
  t.integer :age, limit: 2
end

This migration creates a users table with a name column (string, not null, default Guest) and an age column (integer with 2-byte limit).

Execution Table

Step	Action	Column	Type	Attributes	Result
1	Start migration	-	-	-	Migration file loaded
2	Create table 'users'	-	-	-	Table 'users' created
3	Add column	name	string	null: false, default: "Guest"	Column 'name' added with constraints
4	Add column	age	integer	limit: 2	Column 'age' added with 2-byte integer
5	Run migration	-	-	-	Database schema updated with new table and columns
6	End migration	-	-	-	Migration complete

💡 Migration finishes after all columns and attributes are applied and database schema is updated

Variable Tracker

Variable	Start	After Step 3	After Step 4	Final
users table	none	created	created	created
name column	none	string, null: false, default: Guest	string, null: false, default: Guest	string, null: false, default: Guest
age column	none	none	integer, limit: 2	integer, limit: 2

Key Moments - 3 Insights

Why do we specify 'null: false' for a column?

Specifying 'null: false' means the column cannot have empty values. In the execution_table step 3, this attribute ensures the database requires a value for 'name'.

What does 'limit: 2' mean for an integer column?

'limit: 2' sets the storage size to 2 bytes, which restricts the range of values. Step 4 shows this attribute applied to 'age' to save space.

What happens if we omit 'default' for a column?

If 'default' is omitted, the column has no preset value. Step 3 shows 'default: "Guest"' sets a fallback value; without it, new records need explicit values.

Visual Quiz - 3 Questions

Look at the execution_table, what attributes does the 'name' column have at step 3?

A null: true, no default

B limit: 2

C null: false, default: "Guest"

D unique: true

💡 Hint

Check the Attributes column in execution_table row 3

At which step is the 'age' column added to the table?

A Step 3

B Step 4

C Step 2

D Step 5

💡 Hint

Look at the Action and Column columns in execution_table

If we remove 'null: false' from the 'name' column, what changes in variable_tracker?

A The 'name column' entry would no longer include 'null: false'

B The 'users table' would not be created

C The 'age column' would change type

D No changes at all

💡 Hint

Refer to the 'name column' row in variable_tracker after Step 3

Concept Snapshot

Rails migrations define table columns with types and attributes.
Use syntax like t.string :name, null: false, default: "Guest".
Attributes control nullability, default values, and storage size.
Run migrations to update the database schema.
Attributes ensure data integrity and optimize storage.

Full Transcript

This visual execution shows how Rails migrations create database columns with types and attributes. First, the migration file loads and the users table is created. Then, the name column is added as a string that cannot be null and defaults to 'Guest'. Next, the age column is added as an integer with a 2-byte limit. Running the migration updates the database schema. Variables track the table and columns as they are created and configured. Key points include why null constraints and defaults matter, and how limits affect storage. The quiz tests understanding of these steps and attributes.