On Dec 27, 11:23 am, Mikhail Teterin <usenet+m...@[EMAIL PROTECTED]
>
wrote:
> One could implement such a function, which will be called from the
trigger
> and notify the client program somehow -- "out of band".
>
> That's Arne's idea, and it is doable.
>
> However, I was hoping, something more uniform is already available, but
that
> does not seem to be the case :(
I would solve this a little further upstream, if possible. What, for
example, causes the table to change? Is there someone or something
that creates a transaction that enters data? Could your program become
the "business logic" layer that sits in between that and the database?
|
