On Fri, 4 May 2001 newsreader@mediaone.net wrote:
> It _is_ quite trivial to write a safe perl
> trigger especially because I control both client
> and server end of postgres. With C it
> will be whole new game for me.
I didn't quite follow the original explanation
of what you're doing, but the safeness thing
was more:
You insert row (1,1,1) into table
Your trigger goes off, does something that
doesn't affect this database (say like
writing a file with 1,1,1 or modifying
another database)
You rollback or an error occurs.
The results of your trigger persist, but
the data isn't in the database anymore (well
it is, but marked dead). If you're expecting
that the outside thing is an accurate representation
of the db, you're in trouble.
