> Yeah, that would be my interpretation: the after trigger runs just
> before the transaction commits, and your external PHP program can't
> see the results since they haven't been committed yet. Your description
> makes it sound like the trigger invokes the PHP code synchronously,
> in which case
Mike Nolan <[EMAIL PROTECTED]> writes:
> 3. The 'after insert' trigger on the first table calls another procedure
> using plperlu which in turn executes an external PHP program that
> does a lookup on the 2nd table (using one of the updated values as
> a key) then sends some e-mail. I
