Re: notify clients on database updates

From: roger <vrsr_at_rogerware.com>
Date: Fri, 24 Oct 2003 00:15:06 GMT
Message-ID: <Xns941DB08CD81E0rsrrogerwarecom@204.127.204.17>

Daniel Morgan <damorgan_at_x.washington.edu> wrote in news:1066949322.260859 @yasure:

> roger wrote:
> AFTER UPDATE trigger writes notification to a table
>
> DBMS_PIPE sends communication directly to C program

Thanks for the reply.

Why the intermediary step of writing to the table? Why not just write the notification data to the pipe?

The other way I imagined was to create an external 'C' routine that would queue messages (perhaps to a UNIX pipe:) rather than using the DBMS_PIPE package. But hey, if DBMS_PIPE is easier, that's fine with me:)

Either way - one wrinkle I forsee is that the pipe reader will potentially be notified before the change to the table is comitted, or perhaps even rolled back.

Is there any mechanism to cause a trigger like this to fire only after the transaction is comitted?

I don't see it off hand.

Thanks. Received on Thu Oct 23 2003 - 19:15:06 CDT