Schema builder (columns, types) in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this Laravel migration column definition?

Consider this Laravel migration snippet:

Schema::create('products', function (Blueprint $table) {
  $table->string('name', 100);
  $table->decimal('price', 8, 2);
  $table->timestamps();
});

What will be the SQL column types generated for name and price?

Laravel

Schema::create('products', function (Blueprint $table) {
  $table->string('name', 100);
  $table->decimal('price', 8, 2);
  $table->timestamps();
});

A name: VARCHAR(255), price: DOUBLE

B name: TEXT, price: FLOAT

C name: VARCHAR(100), price: DECIMAL(8,2)

D name: CHAR(100), price: DECIMAL(10,2)

💡 Hint

Look at the parameters passed to string() and decimal() methods.

The string() method with a length parameter creates a VARCHAR column with that length. The decimal() method creates a DECIMAL column with precision and scale as specified.

📝 Syntax

intermediate

Which option correctly defines a nullable integer column in Laravel schema?

You want to add an integer column named age that can be empty (nullable). Which of these Laravel schema builder lines is correct?

A $table->integer('age')->nullable();

B $table->integer('age')->null();

C $table->integer('age', true);

D $table->nullable()->integer('age');

💡 Hint

Check the method chaining order and method names.

The nullable() method is called after defining the column type to allow NULL values. The other options either use wrong method names or wrong order.

🔧 Debug

advanced

Why does this Laravel migration code cause an error?

Examine this migration snippet:

Schema::table('users', function (Blueprint $table) {
  $table->string('email')->unique()->nullable(false);
});

Why will this cause an error or unexpected behavior?

Laravel

Schema::table('users', function (Blueprint $table) {
  $table->string('email')->unique()->nullable(false);
});

A unique() must come after nullable(), order matters

B nullable(false) is invalid; nullable() only accepts no arguments or true

C string() requires a length parameter, missing here

D You cannot add unique constraint in a table modification

💡 Hint

Check the nullable() method signature in Laravel schema builder.

The nullable() method does not accept any arguments. Passing false causes a syntax error or unexpected behavior. To make a column NOT nullable, omit nullable() or use ->nullable(false) is invalid.

❓ state_output

advanced

What is the default value of a boolean column defined like this in Laravel?

Given this migration code:

Schema::create('settings', function (Blueprint $table) {
  $table->boolean('active');
});

What will be the default value of the active column if no default is set explicitly?

Laravel

Schema::create('settings', function (Blueprint $table) {
  $table->boolean('active');
});

A true (1)

B false (0)

C NULL

D No default, insert will fail without value

💡 Hint

Think about how databases handle columns without defaults and NOT nullable.

By default, boolean columns are NOT nullable and have no default value. So inserting a row without specifying 'active' will cause an error.

🧠 Conceptual

expert

Which Laravel schema builder column type should you use for storing large JSON data efficiently?

You want to store large JSON data in a database column using Laravel's schema builder. Which column type is best suited for this purpose?

A $table->jsonb('data');

B $table->text('data');

C $table->json('data');

D $table->longText('data');

💡 Hint

Consider database support for JSON types and efficiency.

The jsonb type stores JSON data in a binary format, allowing indexing and efficient querying, supported in PostgreSQL. json() stores JSON as text without indexing. text() and longText() store plain text without JSON features.