Re: [OT] MySQL is bad, but THIS bad?

* Mark Woodward:

> "On the other hand, you shouldn't use mysql_use_result() if you are doing
> a lot of processing for each row on the client side, or if the output is
> sent to a screen on which the user may type a ^S (stop scroll). This ties
> up the server and prevent other threads from updating any tables from
> which the data is being fetched."
>
> How do busy web sites work like this?

Any system based on locking exhibits this problem. Even with MVCC,
you can run into it if you've got multiple writers. As a rule of
thumb, I never perform network I/O within transactions which update
the database (or "read the database", for systems without MVCC).