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.
(PHP 5 >= 5.1.0, PECL pdo >= 0.2.4)
PDOStatement::fetchObject — Fetches the next row and returns it as an object.
$class_name= "stdClass" [, array
Fetches the next row and returns it as an object. This function is an
alternative to PDOStatement::fetch() with
Name of the created class.
Elements of this array are passed to the constructor.
Returns an instance of the required class with property names that
correspond to the column names ou
FALSE em caso de falha.
- PDOStatement::fetch() - Fetches the next row from a result set