Re: polling, triggers, java, Oracle, C++

This is the method I used and it worked fairly well. However, after I finished, I thought the DBMS_ALERT package would have been a better choice over the DBMS_PIPE package that I used, mainly because DBMS_ALERT is transactional (i.e. the alert always arrives after the commit, pipe messages can arrive before).

"Andrew R. Thomas-Cramer" wrote:

> Have you considered having the trigger do nothing but insert a message into
> a pipe identifying the new record by a unique ID -- and have the process
> that's currently polling for new records instead read messages off the pipe?
>
> argosy22_at_my-deja.com wrote in message <8ilg7j$n44$1_at_nnrp1.deja.com>...
> >The idea is that customers will use the web interface,
> >and insert a record into the database. The polling
> >then checks for new records.
Received on Tue Jun 20 2000 - 00:00:00 CDT