> >> >program). But this didn't work. So I wrote a simple print method that > >> >takes > >> >one argument and printf it to the standard out. This works and actually > >> >solves my problem. > >> There isn't a way to get this output printed directly, but you can > >> easily create a log of your applications activity in a table and then > >> use a select to dump the table. > > > > The problem with logging to a table is that if the transaction aborts > > (ie: because there's a bug in the trigger), you won't get anything in > > the table. So when you need the info most you can't get it.
There's always unix syslog() and the windows event log. With good infrastructure you can view errors remotely too.
