mysql_field_type
I agree with Joachim Kruyswijk (posted on 14-Jun-2005 11:42). I just did the test on my beta version of my new site (who needs to get dynamically news and user login from a database) and i use 1000kb less memory when i do not use mysql_free_result. I guess it is because the data it needs to load are not that large (for news: date, short description and for the user login: username, password). It may only be in the user control panel that it will be more, but since that isn't developed totally yet, i'll have to test :p
mysql_free_result
(PHP 4, PHP 5, PECL mysql:1.0)
mysql_free_result — 释放结果内存
说明
bool mysql_free_result
( resource $result
)
mysql_free_result() 将释放所有与结果标识符 result 所关联的内存。
mysql_free_result() 仅需要在考虑到返回很大的结果集时会占用多少内存时调用。在脚本结束后所有关联的内存都会被自动释放。
如果成功则返回 TRUE，失败则返回 FALSE。
为向下兼容仍然可以使用 mysql_freeresult()，但反对这样做。
add a note
User Contributed Notesmysql_free_result
webmaster at wforums dot net
17-Jun-2008 04:02
17-Jun-2008 04:02
admin at ifyouwantblood dot de
18-Mar-2008 04:47
18-Mar-2008 04:47
yes this function may increase the memory usage if you use unbuffered querys and if you have not fetched all the data from mysql. in this case the mysql api has a problem: you want to free the result but do not want to close the connection. now mysql will only accept another query if all data has been fetched, so the api now must fetch the rest of the data when calling mysql_free_result().
so only use unbuffered querys if you fetch all the data (and need it).
21-Nov-2006 06:53
If you're seeing warnings like "Warning: Unknown: 6 result set(s) not freed. Use mysql_free_result to free result sets which were requested using mysql_query() in Unknown on line 0" and want to turn them off, set mysql.trace_mode = Off in your php.ini
Nairebis
26-Feb-2006 10:00
26-Feb-2006 10:00
ALWAYS use this function! I just encountered a bug in my code where I forgot to use this function. I also happen to be using mysql_pconnect() for a persistent connection. If you forget to free the result, it can hold the old result set open indefinitely within the HTTP process.
The upshot (in my application) was that I did updates that happened in a different HTTP process, but they mysteriously didn't show up in another HTTP process. After panicking that MySQL had mysterious data corruption and/or synchronization problems, I traced it back to this where an old result set was held open.
mdeininger at jyujin dot de
20-Sep-2005 07:45
20-Sep-2005 07:45
yes, i encountered that too. as far as i could tell, that's because the script is stored in memory after being compiled and that's as much more memory as it needs for a call to that function.
if you always get lotsa data in your results, using this function will decrease memory usage tho, unless you use non-buffered queries (which are preferable unless you absolutely *have* to use mysql_seek(), or you need to do another query while the last one hasn't finished reporting back, as they can provide a small speedup)
macronesia at macronesia dot net
03-Jul-2005 03:11
03-Jul-2005 03:11
You not need to use this if you are using PHP 4.
The comment below this comment may explain why it's actually costing more memory.
Joachim Kruyswijk
14-Jun-2005 05:42
14-Jun-2005 05:42
Using this function may actually increase the amount of memory used. In my case, the script used 208 bytes less memory when *not* using mysql_free_result().
Check for yourself: call memory_get_usage() at the end of the script.