Req #51308 [Com]: PDO::FETCH_FUNC should also work with fetch()
| From: | netmosfera at email dot it | Date: | Tue, 14 Jan 2014 06:07:59 +0000 |
| Subject: | Req #51308 [Com]: PDO::FETCH_FUNC should also work with fetch() | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-183780@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=51308&edit=1
ID: 51308
Comment by: netmosfera at email dot it
Reported by: kenaniah at gmail dot com
Summary: PDO::FETCH_FUNC should also work with fetch()
Status: Open
Type: Feature/Change Request
Package: PDO related
Operating System: *
PHP Version: 5.3.2
Block user comment: N
Private report: N
New Comment:
fell in the same problem, it should be supported also by fetch() and setFetchMode()
a function callback is way more flexible than the constructor solution (which works a bit weirdly
also)
please fix this!
Previous Comments:
------------------------------------------------------------------------
[2010-11-15 20:50:41] kenaniah at gmail dot com
jinmoku:
Thanks, but that doesn't solve the problem. Consider the use case in which you
would want to transparently process database results between the database and
PHP. By implementing FETCH_FUNC, one would be able to process the result set
without having to modify every instance where the result is accessed. Your
workaround requires that I modify my code every place I want to pre-process my
results, as opposed to simply modifying the fetch mode on the driver once. As
you could imagine, the workaround would be more of a headache than the actual
bug in a fairly-sized codebase.
------------------------------------------------------------------------
[2010-11-15 01:07:45] jinmoku at hotmail dot com
you can use call_user_func_array :
$db = new PDO(...);
$stmt = $db->execute("SELECT * FROM foobar");
$stmt->setFetchMode(PDO::FETCH_ASSOC);
foreach($stmt as $row):
call_user_func_array('var_dump', $row);
endforeach;
------------------------------------------------------------------------
[2010-11-13 12:41:14] visor at alt22 dot ru
Still reproduced for PHP 5.3.3
------------------------------------------------------------------------
[2010-03-16 18:24:20] kenaniah at gmail dot com
Description:
------------
Currently, PDO::FETCH_FUNC can only be used in the PDOStatement::fetchAll() method. This fetch mode,
however, is essentially useless since it can not be set using setFetchMode() or fetch(), and thus
can not be used in iteration.
Test script:
---------------
<?php
$db = new PDO(...);
$stmt = $db->execute("SELECT * FROM foobar");
$stmt->setFetchMode(PDO::FETCH_FUNC, 'var_dump');
foreach($stmt as $row):
...
endforeach;
?>
Expected result:
----------------
PDO should set the fetch mode to FETCH_FUNC, and should call var_dump() when $stmt is iterated.
Because no additional fetch modes were passed to setFetchMode(), var_dump() should receive an
argument representing the row in PDO::FETCH_BOTH format. $row should be set to the return of
var_dump(), and control should now be passed to the foreach codeblock.
IMHO, FETCH_FUNC should allow one to provide a callback function that allows full manipulation of
the row before being passed into the iteration codeblock. For example, in an active record
implementation, one would have to set the FETCH_CLASS method and suffer a very costly object
instantiation. A callback function would allow me to clone an existing (and fully loaded) object,
set my properties, and return it -- saving me upwards of 90% in execution costs for heavy objects.
Actual result:
--------------
Warning: PDOStatement::setFetchMode() [pdostatement.setfetchmode]: SQLSTATE[HY000]: General error:
PDO::FETCH_FUNC is only allowed in PDOStatement::fetchAll()
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=51308&edit=1