mysql_free_result question

adavis

If my user wants to print a printer-friendly report, then I need to run through my database a second time. I use the one script to build my sql statement (I go through this once) and then use the same script to build the actual report on either page (possibly go through this twice). If I put this statement:

mysql_free_result($result);

just before this statement:

$result = mysql_query($sql,$dblink) or die("Couldn't execute query\n");

will this cause any problems the first time through when $result is empty?

jweissig

why not test it out?

Simple use mysql_free_result($result) and then try and call $result. The best way to learn is to try something.. Even if someone told you would you really beleave them?

Anyways you in luck I will tell you..

PHP Manual -- mysql_free_result

mysql_free_result() will free all memory associated with the result identifier result.

So, Yes.. it will kill the results set 🙂

adavis

I had to figure out where to put the mysql_free_result($result);, but when I finally did, it worked. If you try to free results when there are none to free, you get an error message. I wanted to put it in the include that is used only once, but I ended up putting it at the end of my while loop and had to put it in all 4 report scripts. But yes, I did get it to work. The reason I was hesitant to try it is that this site is already in production and for some reason, this error just started showing up yesterday. It had been working a few weeks ago when I was testing it. The mistake I made was that I didn't test it very well on Netscape or on the Mac, so I decided to run it through those two yesterday and started getting errors that I never saw on IE. Especially on the Mac. I got a bunch of JavaScript errors that I still didn't get on the my PC.