PHP 5.6.18 is available


(PHP 5 >= 5.1.0, PHP 7, PECL pdo >= 0.2.4)

PDOStatement::fetchObjectRécupère la prochaine ligne et la retourne en tant qu'objet


public mixed PDOStatement::fetchObject ([ string $class_name = "stdClass" [, array $ctor_args ]] )

Récupère la prochaine ligne et la retourne en tant qu'objet. Cette fonction est une alternative à PDOStatement::fetch() avec PDO::FETCH_CLASS ou le style PDO::FETCH_OBJ.

Liste de paramètres


Nom de la classe créée.


Éléments de ce tableau sont passés au constructeur.

Valeurs de retour

Retourne une instance de la classe demandée avec les propriétés de noms qui correspondent aux noms des colonnes ou FALSE si une erreur survient.

Voir aussi

add a note add a note

User Contributed Notes 5 notes

rasmus at mindplay dot dk
2 years ago
Be warned of the rather unorthodox behavior of PDOStatement::fetchObject() which injects property-values BEFORE invoking the constructor - in other words, if your class  initializes property-values to defaults in the constructor, you will be overwriting the values injected by fetchObject() !

A var_dump($this) in your __construct() method will reveal that property-values have been initialized prior to calling your constructor, so be careful.

For this reason, I strongly recommend hydrating your objects manually, after retrieving the data as an array, rather than trying to have PDO apply properties directly to your objects.

Clearly somebody thought they were being clever here - allowing you to access hydrated property-values from the constructor. Unfortunately, this is just not how OOP works - the constructor, by definition, is the first method called upon construction.

If you need to initialize your objects after they have been constructed and hydrated, I suggest your model types implement an interface with an init() method, and you data access layer invoke this method (if implemented) after hydrating.
beinghavingbreackfast at gmail dot com
6 months ago
It should be mentioned that this method can set even non-public properties. It may sound strange but it can actually be very useful when creating an object based on mysql result.
Consider a User class:

class User {
// Private properties
private $id, $name;

   private function
__construct () {}

   public static function
load_by_id ($id) {
$stmt = $pdo->prepare('SELECT id, name FROM users WHERE id=?');
/* same method can be written with the "name" column/property */

$user = User::load_by_id(1);

fetchObject() doesn't care about properties being public or not. It just passes the result to the object. Output is like:

object(User)#3 (2) {
  string(1) "1"
  string(10) "John Smith"
dave at davidhbrown dot us
7 months ago
If using a namespaced class, you must provide the fully qualified class name; fetchObject does not seem to know about any "use" statements.

This results in a PHP Fatal error: Class 'MyClass' not found...:
use MyNamespace\MyClass;
// ...
$o = $statement->fetchObject('MyClass'));
This works:
use MyNamespace\MyClass; //still needed for my code
// ...
$o = $statement->fetchObject('MyNamespace\\MyClass'));
10 months ago
I think so could us use this variant to implement the constructor, this is my example:

class User{
    public function
$args = func_get_args();
$nargs = func_num_args();
$attribs = get_class_vars(get_class($this));
$args as $value){
$attrib = key($attribs);
$this->$attrib = $value;
Vegard Lkken
1 year ago
Because of the injection of object properties before the constructor is executed, I usually build my classes like this to make sure already set properties aren't overwritten:

class Person {

  public function
__construct($name=NULL, $age=NULL, $sex=NULL) {
$this->name = $name === NULL ? $this->name : $name;
$this->age = $age === NULL ? $this->age : $age;
$this->sex = $sex === NULL ? $this->sex : $sex;
To Top