Timestamps management in Laravel - Step-by-Step Execution

Concept Flow - Timestamps management

Model Created

↓

Check if timestamps enabled?

No→Skip timestamp update

Yes↓

Set created_at and updated_at to current time

↓

Save model to database

↓

On Model Update

↓

Check if timestamps enabled?

No→Skip timestamp update

Yes↓

Set updated_at to current time

↓

Save changes to database

When a Laravel model is created or updated, it checks if timestamps are enabled. If yes, it sets created_at and updated_at fields automatically before saving.

Execution Sample

Laravel

use Illuminate\Database\Eloquent\Model;

class Post extends Model {
  public $timestamps = true;
}

$post = new Post();
$post->save();

This code creates a new Post model instance and saves it, automatically setting timestamps if enabled.

Execution Table

Step	Action	Timestamps Enabled?	created_at	updated_at	Database Save
1	Create new Post instance	true	null	null	No
2	Check timestamps enabled	true	null	null	No
3	Set created_at and updated_at to now	true	2024-06-01 12:00:00	2024-06-01 12:00:00	No
4	Save Post to database	true	2024-06-01 12:00:00	2024-06-01 12:00:00	Yes
5	Update Post instance	true	2024-06-01 12:00:00	2024-06-01 12:00:00	No
6	Check timestamps enabled	true	2024-06-01 12:00:00	2024-06-01 12:00:00	No
7	Set updated_at to now	true	2024-06-01 12:00:00	2024-06-01 12:05:00	No
8	Save updated Post to database	true	2024-06-01 12:00:00	2024-06-01 12:05:00	Yes
9	Create new Post with timestamps disabled	false	null	null	No
10	Check timestamps enabled	false	null	null	No
11	Skip timestamp setting	false	null	null	No
12	Save Post to database	false	null	null	Yes

💡 Execution stops after saving models; timestamps are set only if enabled.

Variable Tracker

Variable	Start	After Step 3	After Step 4	After Step 7	After Step 8	After Step 11	Final
created_at	null	2024-06-01 12:00:00	2024-06-01 12:00:00	2024-06-01 12:00:00	2024-06-01 12:00:00	null	null
updated_at	null	2024-06-01 12:00:00	2024-06-01 12:00:00	2024-06-01 12:05:00	2024-06-01 12:05:00	null	null
timestamps_enabled	true	true	true	true	true	false	false

Key Moments - 3 Insights

Why are created_at and updated_at set to the same time when creating a new model?

When creating a new model, Laravel sets both created_at and updated_at to the current time because the record is new and just created. See execution_table rows 3 and 4.

What happens if timestamps are disabled on a model?

If timestamps are disabled (timestamps_enabled is false), Laravel skips setting created_at and updated_at fields before saving. See execution_table rows 9 to 12.

Why does updated_at change on update but created_at stays the same?

created_at marks when the record was first created and does not change. updated_at updates every time the record changes. See execution_table rows 7 and 8.

Visual Quiz - 3 Questions

Look at the execution_table at step 3. What are the values of created_at and updated_at?

A "2024-06-01 12:00:00" for both

B "null" for both

C "2024-06-01 12:05:00" for both

D "2024-06-01 12:00:00" for created_at and "null" for updated_at

💡 Hint

Check the 'created_at' and 'updated_at' columns in execution_table row 3.

At which step does the updated_at timestamp get updated after the initial creation?

A Step 4

B Step 3

C Step 7

D Step 11

💡 Hint

Look at the 'updated_at' column changes in execution_table rows 7 and 8.

If timestamps are disabled, what happens to the created_at and updated_at fields when saving?

A They are set to current time

B They remain null

C Only updated_at is set

D created_at is set, updated_at remains null

💡 Hint

See execution_table rows 9 to 12 where timestamps_enabled is false.

Concept Snapshot

Laravel models have automatic timestamps: created_at and updated_at.
When $timestamps = true (default), Laravel sets these fields on create and update.
created_at is set once on creation; updated_at updates on every save.
Disable timestamps by setting public $timestamps = false in the model.
Timestamps help track when records were created and last changed.

Full Transcript

In Laravel, models can automatically manage timestamps for creation and updates. When you create a new model instance and save it, Laravel checks if timestamps are enabled. If yes, it sets both created_at and updated_at fields to the current time before saving. When you update the model later, only updated_at changes to the new current time, while created_at remains the same. If you disable timestamps by setting public $timestamps = false in your model, Laravel skips setting these fields. This helps you track when records were created and last updated without manual work.