Re: Re: Re: Perl dbi disconnect question...

I think you should refactor so that you handle errors with one functions and success with another. Reserve exit(0) for leaving with your utility having done everything your user should expect. You may want to give exit different values to represent differeent errors. 0+$! is a good value if the reason is an error that sets $!. Or you could call die $!, instead.

After Compline,
Zaxo

Comment on Re: Re: Re: Perl dbi disconnect question...

Replies are listed 'Best First'.
Re: Re: Re: Re: Perl dbi disconnect question... by kiat (Vicar) on Jan 05, 2004 at 01:47 UTC
Ah, I see. So I should have a different bail out sub when an error occurs during a query execution. Will the following do? `sub bail_out2 { my $message = shift # output error in html # exit with 1 because it's a failure exit(1); }` [download] Does exiting with the value of 1 automatically kills the database connection? I need to print out the error in html to let the user know that something has gone wrong with the processing of the script. die prints the error to the log which is invisible to the user. Am I right?	[reply] [d/l]

Replies are listed 'Best First'.

Re: Re: Re: Re: Perl dbi disconnect question...
by kiat (Vicar) on Jan 05, 2004 at 01:47 UTC

sub bail_out2 {
  my $message = shift
  # output error in html
  # exit with 1 because it's a failure
  exit(1);
}
[download]

I need to print out the error in html to let the user know that something has gone wrong with the processing of the script. die prints the error to the log which is invisible to the user. Am I right?

[reply]
[d/l]