Content · Web Development · PHP

PHP PDO::errorCode() Method: Usage and Examples

Returns the SQLSTATE code for the most recent operation on the connection. Statement-specific errors belong on PDOStatement; exceptions are preferred for control

1 views Published Oct 17, 2026 Updated Oct 17, 2026 admin

Returns the SQLSTATE code for the most recent operation on the connection.

The objective is to understand the behavior and operational limits, not only the method name.

What It Does


Returns the SQLSTATE code for the most recent operation on the connection.

Syntax and Return Value


PDO::errorCode(): mixed

The return value and exceptional cases depend on the call described here: Statement-specific errors belong on PDOStatement; exceptions are preferred for control flow.

Example 1: Basic Use


This self-contained SQLite example uses in-memory demo data; it requires the pdo_sqlite driver.

<?php
$pdo = new PDO('sqlite::memory:', null, null, [PDO::ATTR_ERRMODE => PDO::ERRMODE_EXCEPTION]);
$pdo->exec('CREATE TABLE products (id INTEGER PRIMARY KEY, name TEXT NOT NULL, price INTEGER NOT NULL, active INTEGER)');
$pdo->exec("INSERT INTO products (id,name,price,active) VALUES (1,'Desk',120,1),(2,'Lamp',35,1),(3,'Chair',85,0)");
$pdo->exec("UPDATE products SET active = 1 WHERE id = 1");
echo $pdo->errorCode() ?? "none";

Example 2: A Second Scenario


This self-contained SQLite example uses in-memory demo data; it requires the pdo_sqlite driver.

<?php
$pdo = new PDO('sqlite::memory:', null, null, [PDO::ATTR_ERRMODE => PDO::ERRMODE_EXCEPTION]);
$pdo->exec('CREATE TABLE products (id INTEGER PRIMARY KEY, name TEXT NOT NULL, price INTEGER NOT NULL, active INTEGER)');
$pdo->exec("INSERT INTO products (id,name,price,active) VALUES (1,'Desk',120,1),(2,'Lamp',35,1),(3,'Chair',85,0)");
$pdo->exec("UPDATE products SET active = 1 WHERE id = 2");
echo $pdo->errorCode() ?? "none";

Example 3: Practical Checks


This self-contained SQLite example uses in-memory demo data; it requires the pdo_sqlite driver.

<?php
$pdo = new PDO('sqlite::memory:', null, null, [PDO::ATTR_ERRMODE => PDO::ERRMODE_EXCEPTION]);
$pdo->exec('CREATE TABLE products (id INTEGER PRIMARY KEY, name TEXT NOT NULL, price INTEGER NOT NULL, active INTEGER)');
$pdo->exec("INSERT INTO products (id,name,price,active) VALUES (1,'Desk',120,1),(2,'Lamp',35,1),(3,'Chair',85,0)");
$pdo->exec("UPDATE products SET active = 1 WHERE id = 3");
echo $pdo->errorCode() ?? "none";

Important Behavior and Edge Cases


Statement-specific errors belong on PDOStatement; exceptions are preferred for control flow.

For production use, also account for error handling, data validation, resource limits and environment-specific driver behavior.

Comparison with Related Approaches


ApproachImportant distinction
PDO::errorCodeReturns the SQLSTATE code for the most recent operation on the connection.
Related API / patternerrorInfo adds driver-specific numeric codes and messages.

Common Beginner Mistakes


MistakeCorrect approach
Assuming the happy path covers edge casesStatement-specific errors belong on PDOStatement; exceptions are preferred for control flow.
Using a related API interchangeablyerrorInfo adds driver-specific numeric codes and messages.

Key Takeaways


  • Returns the SQLSTATE code for the most recent operation on the connection.
  • Statement-specific errors belong on PDOStatement; exceptions are preferred for control flow.
  • errorInfo adds driver-specific numeric codes and messages.

Choose this API or pattern when its exact semantics match your task, and verify the result against the database driver and runtime used by your application.

Share this resourceSend this page to someone who may find it useful.