Database configuration in Laravel - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the default database connection in Laravel's config file.

Laravel

'default' => '[1]',

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

Asqlite

Bpgsql

Csqlsrv

Dmysql

Attempts:

3 left

💡 Hint

Common Mistakes

Using a connection name that is not defined in the connections array.

Leaving the default connection empty.

The 'default' key in config/database.php sets the default database connection. 'mysql' is commonly used.

2fill in blank

medium

Complete the code to specify the database host in Laravel's MySQL connection configuration.

Laravel

'host' => [1],

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

A'192.168.1.1'

B'localhost'

C'127.0.0.1'

D'mysql-server'

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'localhost' which sometimes resolves differently.

Using an incorrect IP address.

The host IP '127.0.0.1' is the loopback address commonly used for local database servers.

3fill in blank

hard

Fix the error in the database username configuration line.

Laravel

'username' => env('[1]', 'root'),

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

ADB_USERNAME

BUSER_NAME

CDATABASE_USER

DDB_USER

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect environment variable names.

Forgetting to set the variable in the .env file.

The environment variable for the database username in Laravel is DB_USERNAME.

4fill in blank

hard

Fill both blanks to configure the database port and charset in Laravel's MySQL connection.

Laravel

'port' => env('[1]', '3306'),
'charset' => '[2]',

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

ADB_PORT

Butf8mb4

Cutf8

DDATABASE_PORT

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'utf8' instead of 'utf8mb4' which lacks full Unicode support.

Using wrong environment variable names for port.

The port environment variable is 'DB_PORT' and the recommended charset is 'utf8mb4' for full Unicode support.

5fill in blank

hard

Fill all three blanks to complete the Laravel database connection array keys for strict mode, engine, and prefix.

Laravel

'strict' => [1],
'engine' => [2],
'prefix' => '[3]',

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

Atrue

Bfalse

Cnull

D""

Attempts:

3 left

💡 Hint

Common Mistakes

Setting strict mode to false when strict SQL is desired.

Using a string 'null' instead of null for engine.

Forgetting to quote the prefix string.

Strict mode is usually set to true for strict SQL mode. Engine can be null to use default. Prefix is an empty string if no prefix is used.

Practice

1. What is the main purpose of the .env file in Laravel's database configuration?

easy

A. To write SQL queries directly

B. To store user session data

C. To define routes for the application

D. To securely store database connection details like username and password

Solution

1. Step 1: Understand the role of the .env file

   The .env file holds environment-specific settings, including sensitive data like database credentials.

2. Step 2: Identify what is stored in .env for database

   It stores host, database name, username, and password securely, keeping them out of code files.

3. Final Answer:

   To securely store database connection details like username and password -> Option D

4. Quick Check:

   .env stores sensitive config = B [OK]

Hint: Remember .env keeps secrets safe, not code or queries [OK]

Common Mistakes:

• Thinking .env stores SQL queries
• Confusing .env with route files
• Assuming .env stores user data

2. Which of the following is the correct way to set the database connection type in Laravel's .env file?

easy

A. DB_CONNECTION=mysql

B. DATABASE=mysql

C. DB_TYPE=mysql

D. CONNECTION_DB=mysql

Solution

1. Step 1: Recall Laravel's .env database config keys

   Laravel uses keys starting with DB_, such as DB_CONNECTION for the driver type.

2. Step 2: Match the correct key for connection type

   The correct key is DB_CONNECTION, set to the database type like mysql, pgsql, sqlite.

3. Final Answer:

   DB_CONNECTION=mysql -> Option A

4. Quick Check:

   DB_CONNECTION sets driver = C [OK]

Hint: DB_CONNECTION is the exact key for database type [OK]

Common Mistakes:

• Using DATABASE or DB_TYPE instead of DB_CONNECTION
• Mixing key order or spelling
• Forgetting to set DB_CONNECTION at all

3. Given this .env snippet:

DB_CONNECTION=pgsql
DB_HOST=127.0.0.1
DB_PORT=5432
DB_DATABASE=mydb
DB_USERNAME=user
DB_PASSWORD=pass

What database type will Laravel connect to?

medium

A. MySQL

B. PostgreSQL

C. SQLite

D. SQL Server

Solution

1. Step 1: Check the DB_CONNECTION value

   The value is 'pgsql', which is the driver name for PostgreSQL in Laravel.

2. Step 2: Match driver to database type

   'pgsql' corresponds to PostgreSQL, not MySQL, SQLite, or SQL Server.

3. Final Answer:

   PostgreSQL -> Option B

4. Quick Check:

   DB_CONNECTION=pgsql means PostgreSQL = A [OK]

Hint: pgsql means PostgreSQL, mysql means MySQL [OK]

Common Mistakes:

• Confusing pgsql with MySQL
• Ignoring DB_CONNECTION value
• Assuming default is MySQL always

4. You wrote this in your .env file:

DB_CONNECTION=mysql
DB_HOST=localhost
DB_PORT=3306
DB_DATABASE=myapp
DB_USERNAME=root
DB_PASSWORD=

But Laravel throws a connection error. What is the most likely cause?

medium

A. Empty DB_PASSWORD causes authentication failure

B. DB_PORT 3306 is incorrect for MySQL

C. DB_HOST should be an IP address, not 'localhost'

D. DB_CONNECTION should be 'pgsql' for MySQL

Solution

1. Step 1: Review the DB_PASSWORD value

   The password is empty, which may cause authentication failure if MySQL requires a password.

2. Step 2: Check other config values

   DB_PORT 3306 is correct for MySQL, DB_HOST 'localhost' is valid, and DB_CONNECTION 'mysql' is correct.

3. Final Answer:

   Empty DB_PASSWORD causes authentication failure -> Option A

4. Quick Check:

   Empty password often blocks login = A [OK]

Hint: Empty password often causes connection errors [OK]

Common Mistakes:

• Assuming port 3306 is wrong
• Thinking localhost is invalid
• Mixing DB_CONNECTION values

5. You want to configure Laravel to use two different databases: one MySQL and one SQLite. How should you set this up in Laravel's configuration?

hard

A. Use only one database type per Laravel project; multiple are not supported

B. Set DB_CONNECTION in .env to both 'mysql,sqlite' separated by comma

C. Define both connections in config/database.php and set DB_CONNECTION in .env to the default

D. Create two separate .env files, one for each database

Solution

1. Step 1: Understand Laravel's multiple connection support

   Laravel supports multiple database connections defined in config/database.php under 'connections'.

2. Step 2: Set default connection in .env and use others explicitly

   DB_CONNECTION in .env sets the default. You can use other connections by specifying their names in code.

3. Final Answer:

   Define both connections in config/database.php and set DB_CONNECTION in .env to the default -> Option C

4. Quick Check:

   Multiple connections in config, default in .env = D [OK]

Hint: Use config/database.php for multiple connections, .env for default [OK]

Common Mistakes:

• Trying to list multiple DB_CONNECTION values in .env
• Creating multiple .env files
• Thinking Laravel can't handle multiple databases