Losing signal from DBMS_ALERT

Let us assume that I have some trigger associated with some table which signals on inserts updates and deletes.

I have an application in Pro*C, which waits for this signal.

Let us assume that I get a signal and I do some processing on this signal.

What happens when the trigger raises another signal while I am processing the first signal.

My understanding is that I will simply lose the second signal.

Is this correct? How do I go about getting rid of this problem?

Basically, I do not ever want to miss changes to the table in question.

thanks,
Senthil

PS: Please do not reply to my email address, because I am sure it is not correct. Received on Tue Jun 09 1998 - 23:37:37 CDT