my loop is a busy wait and keeps iterating until a=b condition is met.
However, it would lead to millions of instructions executing per second.
So to save resources, I want to keep a sleep before re-iterating. Don't understand how is SLEEP disastrous here even if i don't know when is my loop going to end
On 10/10/07, Richard Huxton <dev@archonet.com> wrote: Jasbinder Singh Bali wrote:
> What if its just SLEEP for 1 second. Why would it keep my stored procedure
> hanging ?
Because presumably your loop-condition isn't under your control
(otherwise you wouldn't need to sleep).
Can you *always* guarantee the condition (a=b) will happen within a
reasonable time-frame?
--
Richard Huxton
Archonet Ltd
