Timestamps management in Laravel - Cheat Sheet & Quick Revision

Recall & Review

beginner

What are timestamps in Laravel Eloquent models?

Timestamps are special columns named created_at and updated_at that Laravel automatically manages to record when a record is created and last updated.

beginner

How do you disable automatic timestamps in a Laravel model?

Set the public property <code>public $timestamps = false;</code> inside the model class to stop Laravel from automatically updating <code>created_at</code> and <code>updated_at</code>.

beginner

Which Laravel migration method adds created_at and updated_at columns?

The $table->timestamps(); method adds both created_at and updated_at columns as nullable timestamp fields.

intermediate

How can you customize the names of timestamp columns in Laravel?

Override the <code>const CREATED_AT</code> and <code>const UPDATED_AT</code> constants in your model to use custom column names for timestamps.

intermediate

What happens if you manually set updated_at to null in a Laravel model?

If you set updated_at to null, Laravel will treat it as no update time. But on saving, Laravel will overwrite it with the current timestamp unless timestamps are disabled.

Which columns does Laravel automatically manage for timestamps?

A created_at and updated_at

B created_on and updated_on

C created and modified

D start_time and end_time

Laravel uses created_at and updated_at columns by default to track record creation and updates.

How do you add timestamp columns in a Laravel migration?

A $table->timestamps();

B $table->timestampColumns();

C $table->addTimestamps();

D $table->timeStamps();

The correct method to add created_at and updated_at columns is $table->timestamps();.

To disable automatic timestamps in a Laravel model, you should:

A Remove timestamps columns from the database

B Set public $timestamps = false;

C Override save() method

D Set timestamps to null

Setting public $timestamps = false; in the model disables automatic timestamp updates.

Which constants do you override to rename timestamp columns in Laravel?

A START_TIME and END_TIME

B TIMESTAMP_CREATED and TIMESTAMP_UPDATED

C CREATED_AT and UPDATED_AT

D CREATED_ON and UPDATED_ON

You override const CREATED_AT and const UPDATED_AT in your model to customize timestamp column names.

If you want Laravel to stop updating timestamps but keep the columns, what do you do?

A Override the save method

B Delete the timestamp columns

C Set timestamps to nullable

D Set public $timestamps = false;

Disabling timestamps by setting public $timestamps = false; stops Laravel from updating those columns.

Explain how Laravel manages timestamps in Eloquent models and how you can customize or disable this feature.

Think about the default columns and how Laravel updates them automatically.

Describe the steps to add timestamps to a new Laravel database table and how to prevent Laravel from updating them automatically.

Consider both migration and model changes.

Practice

1. What does the $timestamps property in a Laravel model control?

easy

A. Whether Laravel automatically manages created_at and updated_at columns

B. The timezone used for timestamps

C. The format of the timestamp columns

D. The database connection for timestamp fields

Solution

1. Step 1: Understand the role of $timestamps in Laravel models

   The $timestamps property tells Laravel if it should automatically update created_at and updated_at fields when saving records.

2. Step 2: Identify what $timestamps = false does

   Setting $timestamps = false disables this automatic management, so Laravel won't update those columns.

3. Final Answer:

   Whether Laravel automatically manages created_at and updated_at columns -> Option A

4. Quick Check:

   $timestamps controls auto timestamp updates [OK]

Hint: Remember: $timestamps toggles auto timestamp updates [OK]

Common Mistakes:

• Confusing $timestamps with timezone settings
• Thinking it changes timestamp format
• Assuming it sets database connection

2. Which of the following is the correct way to add timestamp columns in a Laravel migration?

easy

A. $table->timestamp();

B. $table->timestamps();

C. $table->timeStamps();

D. $table->addTimestamps();

Solution

1. Step 1: Recall Laravel migration syntax for timestamps

   Laravel provides a method timestamps() (all lowercase) to add created_at and updated_at columns automatically.

2. Step 2: Check each option's syntax

   $table->timestamps(); uses the correct method name timestamps(). Options A, B, and D are either incomplete or incorrect method names.

3. Final Answer:

   $table->timestamps(); -> Option B

4. Quick Check:

   Migration timestamps method = timestamps() [OK]

Hint: Use exact method timestamps() in migrations [OK]

Common Mistakes:

• Using singular timestamp() instead of plural
• Capitalizing method name incorrectly
• Assuming method is addTimestamps()

3. Given this model code, what will be the value of updated_at after saving a new record?

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

$post = new Post();
$post->title = 'Hello';
$post->save();

medium

A. Null because it is a new record

B. An error occurs because updated_at is not set manually

C. Timestamp of the last update before save

D. Current timestamp when save() is called

Solution

1. Step 1: Understand $timestamps = true effect on saving

   When $timestamps is true, Laravel automatically sets created_at and updated_at to the current time on save.

2. Step 2: Analyze saving a new record

   On creating a new record, both timestamps get the current time. So updated_at is set to now, not null or error.

3. Final Answer:

   Current timestamp when save() is called -> Option D

4. Quick Check:

   New record save updates timestamps automatically [OK]

Hint: New saves set both timestamps to current time [OK]

Common Mistakes:

• Thinking updated_at is null on new records
• Assuming manual setting is required
• Believing an error occurs without manual timestamps

4. You have this migration snippet:

Schema::create('users', function (Blueprint $table) {
  $table->id();
  $table->string('name');
  $table->timestamps;
});

What is the problem here?

medium

A. You must add nullable() to timestamps

B. The timestamps method does not exist

C. Missing parentheses after timestamps method call

D. The id() method should come after timestamps

Solution

1. Step 1: Check the migration method call syntax

   In Laravel migrations, timestamps() is a method and must be called with parentheses.

2. Step 2: Identify the error in the code

   The code uses $table->timestamps; without parentheses, so it does not execute the method, causing no timestamp columns to be created.

3. Final Answer:

   Missing parentheses after timestamps method call -> Option C

4. Quick Check:

   Method calls need parentheses: timestamps() [OK]

Hint: Always add () when calling migration methods [OK]

Common Mistakes:

• Forgetting parentheses on method calls
• Thinking timestamps is a property, not a method
• Assuming order of columns matters here

5. You want to disable automatic timestamp management for a model but still keep the created_at and updated_at columns in the database. How should you do this?

hard

A. Set public $timestamps = false; in the model and keep $table->timestamps() in migration

B. Remove $table->timestamps() from migration and set $timestamps = false in model

C. Set public $timestamps = true; and manually update timestamps in code

D. Rename created_at and updated_at columns to disable timestamps

Solution

1. Step 1: Understand disabling timestamps in model

   Setting public $timestamps = false; in the model disables Laravel's automatic update of timestamp columns.

2. Step 2: Keep timestamp columns in database

   Keeping $table->timestamps() in migration ensures the columns exist in the database even if Laravel does not update them automatically.

3. Final Answer:

   Set public $timestamps = false; in the model and keep $table->timestamps() in migration -> Option A

4. Quick Check:

   Disable auto timestamps in model, keep columns in migration [OK]

Hint: Disable in model, keep columns in migration to keep timestamps [OK]

Common Mistakes:

• Removing timestamps columns from migration when disabling
• Assuming setting $timestamps to true disables timestamps
• Renaming columns to disable timestamps