Re: DB, MDB2, PDO - Future of DB-Abstraction in PEAR

From: Date: Thu, 01 Sep 2005 14:24:59 +0000
Subject: Re: DB, MDB2, PDO - Future of DB-Abstraction in PEAR
References: 1 2  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-39679@lists.php.net to get a copy of this message
Lukas Smith wrote:
[set a default FetchMode in PDO class] http://pecl.php.net/bugs/bug.php?id=4732
[set Statement class in query() too, not only in prepare(), or set Statement class by a PDO attribute] http://pecl.php.net/bugs/bug.php?id=4987
I am quite certain that both of these will be addressed.
sadly looks like if you were wrong. I cannot really understand why. Particularly if you can't change the hardcoded default FetchMode many people must either wrap PDO or spread PDOStatement::setFetchMode() calls (or additional parameters to all PDOStatement::fetch() calls) all over their code. Of course I perfectly understand that a stable PDO has the highest priority now and devs have other things to, particularly if they themselfes only use the hardcoded FetchMode or own wrapper-classes / DB-frameworks. But for me this is the only real problem with the PDO API, preventing me from using it directly, making it necessary to use a wrapper class. All OOP DB-abstractions I have used have something like that, extensions have dedicated methodes for different FetchModes (like fetch_[assoc|object|row]()... in mysql, mysqli, oci, pgsql, sqlite...), which is not as nice as having a default FetchMode (IMHO). Perhaps it helps if I'd try to write a patch for that, but I'm not a C programmer... Best regards Andreas

« previous php.pear.dev (#39679) next »