Timestamps management in Laravel - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable automatic timestamps in a Laravel model.

Laravel

class Post extends Model {
    public $[1] = true;
}

Drag options to blanks, or click blank then click option'

AsoftDeletes

Btimestamps

Cfillable

Dguarded

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'softDeletes' instead of 'timestamps'.

Forgetting to set the property as public.

Confusing 'fillable' with timestamp management.

Setting public $timestamps = true; in a Laravel model enables automatic management of created_at and updated_at timestamps.

2fill in blank

medium

Complete the code to disable timestamps in a Laravel model.

Laravel

class Comment extends Model {
    public $[1] = false;
}

Drag options to blanks, or click blank then click option'

Atimestamps

Bhidden

CsoftDeletes

Dincrementing

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'softDeletes' instead of 'timestamps'.

Setting the property to true instead of false.

Confusing 'incrementing' with timestamp control.

Setting public $timestamps = false; disables automatic timestamp management in Laravel models.

3fill in blank

hard

Fix the error in the code to correctly set a custom timestamp column name.

Laravel

class User extends Model {
    const CREATED_AT = '[1]';
}

Drag options to blanks, or click blank then click option'

Acreated_at

BcreatedAt

CcreatedAtAt

Dcreate_at

Attempts:

3 left

💡 Hint

Common Mistakes

Using camelCase instead of snake_case.

Misspelling the column name.

Adding extra letters or missing underscores.

The default Laravel timestamp column is created_at. To customize it, set const CREATED_AT = 'created_at'; or your custom column name.

4fill in blank

hard

Fill both blanks to customize the timestamp column names for created and updated times.

Laravel

class Article extends Model {
    const CREATED_AT = '[1]';
    const UPDATED_AT = '[2]';
}

Drag options to blanks, or click blank then click option'

Acreated_on

Bupdated_on

Cupdated_at

Dcreated_at

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up created and updated constants.

Using camelCase instead of snake_case.

Not matching the database column names exactly.

To customize timestamp columns, set CREATED_AT and UPDATED_AT constants to your desired column names like created_on and updated_on.

5fill in blank

hard

Fill all three blanks to create a model that disables timestamps and sets a custom date format.

Laravel

class Event extends Model {
    public $[1] = [2];
    protected $dateFormat = '[3]';
}

Drag options to blanks, or click blank then click option'

Atimestamps

Bfalse

CY-m-d H:i:s

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Setting timestamps to true instead of false.

Using an invalid date format string.

Confusing public and protected visibility.

To disable timestamps, set public $timestamps = false;. To customize the date format, set protected $dateFormat to a valid PHP date format string like Y-m-d H:i:s.

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