[Solved] Find the mistake in this migration snippet:$table->integer('age')->nullable(false)->default(null); — Ans: Setting nullable(false) conflicts with default(null) | Laravel

Laravel - Database Basics and Migrations

Find the mistake in this migration snippet:

$table->integer('age')->nullable(false)->default(null);

Adefault(null) is invalid syntax

Binteger() cannot have default values

CSetting nullable(false) conflicts with default(null)

Dnullable() must be true to allow nulls

Step-by-Step Solution

Solution:

Step 1: Analyze nullable and default usage
Setting nullable(false) means the column cannot be null.
Step 2: Check default value compatibility
Setting default(null) conflicts because null is not allowed.
Final Answer:
Setting nullable(false) conflicts with default(null) -> Option C
Quick Check:
nullable(false) disallows null, default(null) conflicts [OK]

Quick Trick: nullable(false) disallows null, so default(null) is invalid [OK]

Common Mistakes:

Master "Database Basics and Migrations" in Laravel

9 interactive learning modes - each teaches the same concept differently

More Laravel Quizzes

Find the mistake in this migration snippet: