php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #54964 PDO does not use defined class, but instead returns anonymous class
Submitted: 2011-05-31 16:34 UTC Modified: 2020-03-13 13:57 UTC
From: daveb at bulmore dot net Assigned: cmb (profile)
Status: Not a bug Package: PDO MySQL
PHP Version: 5.3.6 OS:
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: daveb at bulmore dot net
New email:
PHP Version: OS:

 

 [2011-05-31 16:34 UTC] daveb at bulmore dot net
Description:
------------
PDO fetch object methods do not use the class defined:

  // not used, but should be
  class User {
    public $username;
    public $first_name;
    public $last_name;
    public $created;
  }

  $stmt->setFetchMode(PDO::FETCH_CLASS, 'User');

  $obj = $stmt->fetch(); //returns anonymous class

but instead use a generated anonymous class based on the select statement.

Test script:
---------------
<pre>
<?php
  class User {
    public $username;
    public $first_name;
    public $last_name;
    public $created;
  }

  $dbh = new PDO("mysql:host=localhost;dbname=testdb;", "test", "test");

  $stmt = $dbh->query('select * from users');

  $stmt->setFetchMode(PDO::FETCH_CLASS, 'User');
  
  foreach ($stmt as $obj)       //or while ($obj = $stmt->fetch())
    {
      echo $obj->username, " ",
           $obj->first_name, " ",
           $obj->last_name, " ",
           $obj->role, " ",
           $obj->verified, " ",
           $obj->trusted, " ",
           $obj->created, "\n";
    }

  $dbh = null;
?>
</pre>

<!--
CREATE TABLE `users` (
  `username` varchar(40) NOT NULL,
  `password` varchar(40) NOT NULL,
  `first_name` varchar(40) DEFAULT NULL,
  `last_name` varchar(60) DEFAULT NULL,
  `email` varchar(255) DEFAULT NULL,
  `role` varchar(20) NOT NULL DEFAULT 'user',
  `verified` varchar(50) NOT NULL DEFAULT 'false',
  `trusted` varchar(5) NOT NULL DEFAULT 'false',
  `created` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  PRIMARY KEY (`username`)
);
-->



Expected result:
----------------
Should get an instance of:

  class User {
    public $username;
    public $first_name;
    public $last_name;
    public $created;
  }

and an error when trying to access the properties:

   $obj->role
   $obj->verified
   $obj->trusted


Actual result:
--------------
Returns an anonymous class with anything that's defined in the select statement.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2011-06-02 07:04 UTC] daveb at bulmore dot net
It appears that the PDO methods return the class, but may also be proxying values from the database.  So there may or may not be a problem.
 [2014-01-01 12:44 UTC] felipe@php.net
-Package: PDO related +Package: PDO MySQL
 [2019-11-05 15:42 UTC] camporter1 at gmail dot com
The behavior here seems to be that when fetching a class, there's no concern for whether columns match properties defined on the class. The rows are proper classes of the object, it's just that additional columns will be added to the objects as undefined properties, which PHP allows.

You can verify this by reflecting on a fetched row and verifying that the class matches.
 [2020-03-13 13:57 UTC] cmb@php.net
-Status: Open +Status: Not a bug -Assigned To: +Assigned To: cmb
 [2020-03-13 13:57 UTC] cmb@php.net
Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to report
a bug at http://bugs.php.net/how-to-report.php

Like camporter1 said (but s/undefined properties/undeclared properties).
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Tue Dec 10 19:01:27 2024 UTC