PDO concerns

From: Date: Sun, 27 Feb 2005 23:44:38 +0000
Subject: PDO concerns
Groups: php.pecl.dev 
Request: Send a blank email to pecl-dev+get-2083@lists.php.net to get a copy of this message
I have been playing with PDO a bit lately and have some real concerns about its consistency with other php functions and code. I refer to 2 bug reports submitted to me on this First http://pecl.php.net/bugs/bug.php?id=3564 MySQL in php has always supported the use of rowCount() to return the number of results in a SELECT, to change this behaviour all of a sudden in PDO is going to cause some confusion to say the least. PDO as I knew it is not a "abstraction" layer but instead a common method of database access that is supposed to support all features of each database even if some features are not portable. Half the agruements for doing PDO to begin with that I have seen are claims that it is not a abstraction layer and not meant to be portable but can be at the programmers choice.. So why remove functionality that has always existed in MySQL access functions before? Next http://pecl.php.net/bugs/bug.php?id=3565 You can not do multiple querys without declaring your $return variable as null hence destorying the prior object. Now this one I may be off but no where have I ever seen a php method act in such a manner before at the very least this needs some very good doc's. What confuses me the most, this only affects the query statement not executes which is inconsistant. -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 266.5.0 - Release Date: 2/25/2005

« previous php.pecl.dev (#2083) next »