To handle PHP database errors, use PDO or MySQLi's try-catch mechanism 1. Set PDO's ERRMODE to an exception and catch 2. Enable MySQLi's strict mode and catch mysqli_sql_exception 3. Disable error display in production environment and log to log files 4. Show users a friendly prompt instead of the original error message 5. Clearly handle connection failures to avoid the program's execution. These methods ensure that errors are captured in a timely manner, recorded securely, and improve application robustness.

Handling database errors in PHP is a cruel part of building reliable and secure web applications. Ignoring or mishandling errors can lead to confusing bugs, data corruption, or even security vulnerabilities. The key is to catch issues early, log them properly, and avoid exposing sensitive details to end users.

Use Try-Catch Blocks with PDO or MySQLi

If you're using PDO or MySQLi (which you should be), exceptions are your best friend when it comes to handling database errors.

With PDO , you can set the error mode to throw exceptions:

 $pdo = new PDO('mysql:host=localhost;dbname=test', 'user', 'pass');
$pdo->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);

Now any database error will throw a PDOException , which you can catch:

 try {
    $stmt = $pdo->query("SELECT * FROM nonexistent_table");
} catch (PDOException $e) {
    echo "Database error: " . $e->getMessage();
}

With MySQLi , while it doesn't throw exceptions by default, you can enable them:

 mysqli_report(MYSQLI_REPORT_ERROR | MYSQLI_REPORT_STRICT);
try {
    $mysqli = new mysqli("localhost", "user", "pass", "test");
    $mysqli->query("SELECT * FROM nonexistent_table");
} catch (mysqli_sql_exception $e) {
    echo "Database error: " . $e->getMessage();
}

This approach ensures that all database problems are handled gracefully instead of letting PHP fail silently.

Log Errors Instead of Displaying Them Publicly

While debugging, showing errors on screen might help, but in production, it's dangerous. Exposing SQL errors can give attackers clues about your database structure.

Instead, log errors to a file or monitoring system:

 error_reporting(E_ALL);
ini_set('display_errors', 0);
ini_set('log_errors', 1);
ini_set('error_log', '/path/to/your/php-error.log');

Then in your try-catch block, you can log the error:

 catch (PDOException $e) {
    error_log("Database error: " . $e->getMessage());
    echo "Something went wrong. Please try again later.";
}

This keeps things quiet for users but give you insight into what went wrong.

Provide User-Friendly Feedback

When something goes wrong, users don't need to see the raw SQL error. They just want to know that there was an issue and maybe what they can do about it.

Examples:

• Instead of “SQLSTATE[42S02]: Base table 'users' not found”, show “We're having trouble loading your data. Please try again.”
• If validation failed before querying, let them know they missed a required field.

You can store friendly messages separately from technical ones, especially if you're logging internally and showing generic notices externally.

Don't Ignore Connection Failures

Connecting to the database is often the first step — and one of the most critical. If it fails, your app can't proceed.

Make sure to handle connection failures explicitly:

• Retry logic? Maybe, but keep it simple.
• Graceful shutdown: inform the user and stop further execution.

Example:

 try {
    $pdo = new PDO("mysql:host=localhost;dbname=app", "user", "pass");
} catch (PDOException $e) {
    error_log("Connection failed: " . $e->getMessage());
    die("Could not connect to the database. Please check back soon.");
}

Avoid using or die() with raw MySQL functions — modern approaches like PDO and MySQLi make this much cleaner.

Handling database errors in PHP doesn't have to be complicated. It's mostly about consistency: always use prepared statements, always catch exceptions, always log what went wrong, and never expose internal details to users. Once you get these patterns down, debugging becomes easier and your apps more robust.

Basically that's it.

The above is the detailed content of How do I handle database errors in PHP?. For more information, please follow other related articles on the PHP Chinese website!