> > Are you saying you want the database to PUSH data to the clients?
> DBMS'
> > don't work that way - they are a pull only architecture.
> David,
> I suspect I do not have nearly the experience you do - so please
> forgive any ignorance...
> POST_EVENT can be declared inside a Stored Procedure. POST_EVENT can
> also take input variable: So, inside an SP, and after COMMIT
> POST_EVENT :STOCK_ID
> should notify any client that has subscribed to EventName = :STOCK_ID
> So, in this instance the DB is 'pushing' info to the client. (or, am I
> way of the mark here?)
> Is someone using Events in this manner??
> TIA
>

the client would need to continuously be registering/unregistering interest
in an event. Never done this but maybe it's possible.
Alan