Comments on: PHP Large result sets and summary tables.

By: v

Mon, 01 Oct 2007 07:53:03 +0000

Great tip. If I could combine that with my other half of the battle, perhaps I could solve the PHP timeout issue when dealing with exporting/importing giant datasets to the browser. There is PHP processing involved.

By: Charles Rowe dot com » Unbuffered result sets in MySQL? I must have been last to know…

Mon, 09 Jul 2007 01:34:16 +0000

[...] Zaitsev over at MySQL Performance Blog has a post entitled PHP Large Result Sets and Summary Tables. This post completely caught me by surprise because (embarrassingly enough) I had no idea you could [...]

By: MySQL Performance Blog » MySQL net_write_timeout vs wait_timeout and protocol notes

Sun, 08 Jul 2007 23:21:34 +0000

[...] my previous post I mentioned you might need to increase net_write_timeout to avoid connection being aborted and now [...]

By: peter

peter — Sat, 07 Jul 2007 08:12:37 +0000

rockerBOO,

Yes sure INSERT SELECT does not work for 2 servers, this is why you can try using FEDERATED or use scripts all together.

By: peter

peter — Sat, 07 Jul 2007 08:10:16 +0000

Harrison, Scott,

Yes that was a typo. I meant to later write about mysql_use_result gotchas so I mentioned it in the wrong place.
Now fixed.

By: Scott

Scott — Sat, 07 Jul 2007 03:04:41 +0000

Yes, Harrison is right. That one jumped out at me as well. mysql_store_result() buffers the entire set so that you can use mysql_num_rows() and mysql_data_seek(). The rest of the gotchas mentioned do apply to mysql_use_result().

By: rockerBOO

rockerBOO — Fri, 06 Jul 2007 21:15:31 +0000

It is also good to note that INSERT INTO SELECT x FROM will not work from my experience on 2 servers with different hosts.

By: Harrison Fisk

Harrison Fisk — Fri, 06 Jul 2007 20:30:17 +0000

Good blog as always Peter. Just commenting cause I think you have slight error when you said that mysql_query uses the mysql_use_result C API. It actually uses the mysql_store_result, and hence takes a lot of memory.