Edit report at https://bugs.php.net/bug.php?id=19777&edit=1
ID: 19777 Comment by: vitor dot luis98 at gmail dot com Reported by: bav at graphit dot ru Summary: We need mysql_fetch_all($mysql_result,[TYPE]) Status: Wont fix Type: Feature/Change Request Package: Feature/Change Request Operating System: All PHP Version: 4CVS-2002-10-06 Block user comment: N Private report: N New Comment: We need urgent mysql_fetch_all, I think it past time to have it. Equals pg_fetch_all. Please o/ Previous Comments: ------------------------------------------------------------------------ [2011-09-30 20:36:59] risto78 at gmail dot com see http://php.net/manual/en/mysqli-result.fetch-all.php ------------------------------------------------------------------------ [2011-09-30 20:29:52] risto78 at gmail dot com the function overhead alone of calling this function in a loop several thousand times should be enough to make a mysql_fetch_all function ------------------------------------------------------------------------ [2010-12-19 06:49:58] hafizanil at hotmail dot com Currently on 2010.Everything data fetch in json.If the mysql result can directly push to json data.It much speedier then looping the data and json_encode it again. ------------------------------------------------------------------------ [2002-10-10 09:03:28] bav at graphit dot ru Sorry, but I see an advantage. Only one - speed. Yes, I know, I can write php function for fetching :) We are not idiots :) ------------------------------------------------------------------------ [2002-10-06 14:14:04] ge...@php.net Looks like the only reason is, that you don't want to write an addidtional line to fetch the rows in a loop. Do you see any other benefits?! I only see disadvantages... if you need such functionality, why don't write a php-function for?! Personally I don't know any Database, which supports such kind of functionality; who ever introduced such a function in pgsql must be drunk :) ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=19777 -- Edit this bug report at https://bugs.php.net/bug.php?id=19777&edit=1
