PHP 8.4.2 Released!

    PDOStatement::errorInfo

    (PHP 5 >= 5.1.0, PHP 7, PHP 8, PECL pdo >= 0.1.0)

    PDOStatement::errorInfo — Fetch extended error information associated with the last operation on the statement handle

    Descrizione

    public PDOStatement::errorInfo(): array

    Elenco dei parametri

    Questa funzione non contiene parametri.

    Valori restituiti

    PDOStatement::errorInfo() returns an array of error information about the last operation performed by this statement handle. The array consists of at least the following fields:

    Element Information
    0 SQLSTATE error code (a five characters alphanumeric identifier defined in the ANSI SQL standard).
    1 Driver specific error code.
    2 Driver specific error message.

    Esempi

    Example #1 Displaying errorInfo() fields for a PDO_ODBC connection to a DB2 database

    <?php
    /* Provoke an error -- the BONES table does not exist */
    $sth = $dbh->prepare('SELECT skull FROM bones');
    $sth->execute();

    echo     "\nPDOStatement::errorInfo():\n";
    $arr = $sth->errorInfo();
    print_r($arr);
    ?>

    Il precedente esempio visualizzerà:

    PDOStatement::errorInfo():
Array
(
    [0] => 42S02
    [1] => -204
    [2] => [IBM][CLI Driver][DB2/LINUX] SQL0204N  "DANIELS.BONES" is an undefined name.  SQLSTATE=42704
)

    Vedere anche:

    • PDO::errorCode() - Fetch the SQLSTATE associated with the last operation on the database handle
    • PDO::errorInfo() - Fetch extended error information associated with the last operation on the database handle
    • PDOStatement::errorCode() - Fetch the SQLSTATE associated with the last operation on the statement handle

    Found A Problem?

    Learn How To Improve This Page • Submit a Pull Request • Report a Bug
    ＋add a note

    User Contributed Notes 3 notes

    up
    16
    Geoffrey Hoffman
    9 years ago
    If your query is successful, PDO::errorInfo() still returns an array. For MySQL 5.x, I get the following...

    Array
    (
    [0] => 00000
    [1] =>
    [2] =>
    )
    up
    8
    richardverason at gmail dot com
    5 years ago
    Seriously errorInfo is your friend. Use it.

    If these look like your google searches then you need errorInfo

    "no database error showing in php"
    "pdo selects from database but wont insert"
    "pdo insert not working"
    "isnt pdo just a big hype, should I go back to mysql?"
    "how much do surgeons make?"

    Trust me it will definitely save you hours of insanity if you make it a habit to use it in development. Forget E-ALL, it failed me since well, E-ALL apparently doesn't know that I didn't set a default value in my MySQL table and my query wasnt adding anything to it. So always do this

    <?php

    $sql     = 'do something on a mysql table where foo = :bar';
    $stmt = prepare($sql);
    $stmt->bindValue(':bar', $foo, PDO::PARAM_[DATA TYPE]);
    $stmt->execute();

    // very important during development. But take it off in production
    $foo_arr = $stmt->errorInfo();
    print_r($foo_arr);

    //Sample print_r return
    /*
    Array(
    [0] => HY000
    [1] => 1364
    [2] => Field 'phone' doesn't have a default value
    )
    Never have I been so happy to see an error
    */
    ?>

    While its common practice for any decent developer to always watch out and try to catch for errors, even the best of us make mistakes. This is not a replacement for exceptions, but the simplicity is priceless.
    ＋add a note
    To Top