my $attr = { PrintError => 0, RaiseError => 1, AutoCommit => 0 };
my $dbh = DBI->connect( @{$login}, $attr )
or die "Can't connect to Oracle database: $DBI::errstr\n";then when an error occurs it will not print to STDERR. Rather it can be read thru $dbh->errstr.
Programming the Perl DBI covers this in better detail. it is also detail in the DBI manpage I believe.
Rao, Dinesh - eSpeed wrote:
Thanks Dave for reminding me of error redirection, how stupid of me.
I would be more than happy to get rid of such a signature :)
Thanks -Dinesh
-----Original Message----- From: David N Murray [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 01, 2003 10:46 AM To: Rao, Dinesh - eSpeed Cc: [EMAIL PROTECTED] Subject: Re: writing errors to a file.
Not a DBI question, but what platform?
Un*x: perl script.pl > logfile 2>&1
Windows: perl script.pl > logfile 2>&1
If you want errors to a different logfile, or output to come to the screen with errors to a logfile, perl script.pl 2>error_log
HTH, Dave
p.s. BTW, that's quite a sig you have.
On Jul 1, Rao, Dinesh - eSpeed scribed:
Hi!
I have a DBI program which connects to Sybase database and executes a procedure, if the procedure execution fails, it automatically throws an error on my screen, but I want this error to be written to a log file, how do I write these error messages to a file ?
Thanks much -Dinesh
CONFIDENTIAL: This e-mail, including its contents and attachments, if any, are confidential. If you are not the named recipient please notify the sender and immediately delete it. You may not disseminate, distribute, or forward this e-mail message or disclose its contents to anybody else. Copyright and any other intellectual property rights in its contents are the sole property of eSpeed, Inc.
E-mail transmission cannot be guaranteed to be secure or error-free. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.
Although we routinely screen for viruses, addressees should check this e-mail and any attachments for viruses. We make no representation or warranty as to the absence of viruses in this e-mail or any attachments. Please note that to ensure regulatory compliance and for the protection of our customers and business, we may monitor and read e-mails sent to and from our server(s).
For further important information, please see http://www.espeed.com/full-disclaimer.html
