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.

Practice

1. Which column type in Rails is best suited to store true or false values?

easy

A. boolean

B. string

C. integer

D. text

Solution

1. Step 1: Understand column types for data

   Boolean columns store true or false values, perfect for yes/no data.

2. Step 2: Compare with other types

   String and text store text, integer stores numbers, so they don't fit true/false data.

3. Final Answer:

   boolean -> Option A

4. Quick Check:

   Boolean = true/false [OK]

Hint: True/false data uses boolean type in Rails [OK]

Common Mistakes:

• Choosing string or text for true/false data
• Using integer to represent boolean values
• Confusing text with boolean type

2. Which of the following is the correct syntax to add a non-nullable string column named title with a default value 'Untitled' in a Rails migration?

easy

A. add_column :books, :title, :text, null: false, default: 'Untitled'

B. add_column :books, :title, :string, default: 'Untitled', null: true

C. add_column :books, :title, :string, null: false, default: 'Untitled'

D. add_column :books, :title, :string, null: false

Solution

1. Step 1: Identify correct column type and options

   We want a string type with null: false and default: 'Untitled'.

2. Step 2: Check syntax order and options

   add_column :books, :title, :string, null: false, default: 'Untitled' correctly uses :string, null: false, and default: 'Untitled'. The option with null: true allows null values. The option with :text uses the wrong type. The option without default misses the default value.

3. Final Answer:

   add_column :books, :title, :string, null: false, default: 'Untitled' -> Option C

4. Quick Check:

   Correct syntax with null and default options [OK]

Hint: Use null: false and default: 'value' together in add_column [OK]

Common Mistakes:

• Forgetting null: false for required columns
• Using wrong column type like text instead of string
• Omitting default value when needed

3. Given this migration snippet:

create_table :users do |t|
  t.integer :age, null: false, default: 18
  t.boolean :active, default: true
end

What will be the default value of active for a new user if not specified?

medium

A. true

B. false

C. nil

D. 0

Solution

1. Step 1: Read the default value for active

   The migration sets default: true for the boolean column active.

2. Step 2: Understand default behavior

   If no value is given when creating a user, active will be set to true automatically.

3. Final Answer:

   true -> Option A

4. Quick Check:

   Boolean default true means new records get true [OK]

Hint: Default value sets initial data if none provided [OK]

Common Mistakes:

• Assuming default is false if not specified
• Confusing nil with default value
• Thinking integer 0 is default for boolean

4. You wrote this migration line:

add_column :orders, :price, :integer, null: true, default: 0

But you want to ensure price is always set and never null. What is the fix?

medium

A. Add null: true, default: nil

B. Change null: true to null: false

C. Change :integer to :float

D. Remove default: 0

Solution

1. Step 1: Identify null constraint

   Currently null: true allows price to be null, which is not desired.

2. Step 2: Fix null constraint

   Changing null: true to null: false ensures price cannot be null.

3. Final Answer:

   Change null: true to null: false -> Option B

4. Quick Check:

   Use null: false to prevent null values [OK]

Hint: null: false means column must have a value [OK]

Common Mistakes:

• Leaving null: true when value must be required
• Removing default without fixing null
• Changing type without addressing null

5. You want to add a status column to your tasks table that stores short text but limits it to 10 characters, defaults to 'pending', and cannot be null. Which migration line is correct?

hard

A. add_column :tasks, :status, :string, limit: 255, null: false, default: 'pending'

B. add_column :tasks, :status, :text, null: false, default: 'pending'

C. add_column :tasks, :status, :string, null: true, default: 'pending'

D. add_column :tasks, :status, :string, limit: 10, null: false, default: 'pending'

Solution

1. Step 1: Choose correct column type and limit

   Use :string with limit: 10 to restrict text length to 10 characters.

2. Step 2: Set null and default options

   Set null: false to require a value and default: 'pending' for initial value.

3. Final Answer:

   add_column :tasks, :status, :string, limit: 10, null: false, default: 'pending' -> Option D

4. Quick Check:

   String with limit, null false, and default set [OK]

Hint: Use limit to restrict string length in migrations [OK]

Common Mistakes:

• Using text type which ignores limit
• Allowing null when value is required
• Setting wrong limit size