Re: How to delay the execution of an SQL statement?

"Jonathan Lewis" <jonathan_at_jlcomp.demon.co.uk> wrote in message news:1020348978.10416.1.nnrp-14.9e984b29_at_news.demon.co.uk...
>
> I think dbms_lock.sleep (or user_lock.sleep)
> have already been mentioned, and these
> are accurate to 0.01 seconds. (Although one
> takes its input in seconds and the other in
> hundredths).
>
> You do have to be careful about procedures
> that sleep and poll though - you can get
> caught by KGL (internal) locks if you need
> to recompile them or things they are dependent
> on. Make sure you have an even that makes them
> shut themselves down.
>
> An alternative to the 'waiting cheaply' for a user
> event is the dbms_alert package. Your waiter
> could register an interest in an alert, then wait
> on it. Your other process could then raise an
> alert when it does the critical event. This may
> be cleaner than writing your own mechanism.
>

Thanks for the suggestion, I didn't read the whole thread so I didn't notice it before.

Bye,
Flavio Received on Fri May 03 2002 - 07:09:24 CDT