Filehandle Filter cuts more to the chase and if you go to Filter::Handle by brott and read the doc there's even an example on how to put a Filehandle's output to a string and at that point, an array is trivial.

I preach using RaiseError until the code goes to production. Why? Because I don't want my scripts to produce any output until it is clean. Thus, the result will oft be located in the apache error-log.

jettero doesn't want this to happen, so first he should set RaiseError => 0. (Btw, I don't use PrintError since RaiseError does the same with a warn.) Now, after each DBI prepare and do, a good little coder will test for success, and finding there is none means it's time to put the $DBI::errstr into whatever container you're using to hold all errors. (This is only valid if a single error is not going to kill the rest of the script) Then, lo you may print the container of errors to STDOUT along with everything else.

While jettero's answer does handle properly, it's also what signalled that he is using RaiseError. I'm advocating this method since some errors may need to be handled differently (ie - stop execution of the script) than others. His own answer to his question is probably valid in the sense that he may not have this requirement.

ALL HAIL BRAK!!!

Update: Added clarification after seeing jettero's response. Left original post for context.

Would something like this help?

  $errfile = qw( stderr.log ); 

  open STDERR, ">$errfile"; 

  die "And in that sleep of death, who knows what dreams may come...";
[download]

Clarification:

Sorry about the mixup. Here's something crude that seems to work on my machine. YMMV

#!\usr\bin\perl
my @errors = ();
my $ctr = 0;

for ( $ctr = 0; $ctr < 10; $ctr += 1 ) {
   eval {
      if ( $ctr == 5 ) {
         die "Number 5 is not alive.";
      }
   };

   if ( $@ ) {
      push ( @errors, $@ );
   }
}

$ctr = @errors;
if ( $ctr != 0 )
   { for ( @errors ) { print "$_\n"; } 
   }
else
   { print "No errors found."; }
[download]

As I said, it's a bit tortured, but the idea is to wrap the DBI stuff into an eval block, pushing the problems onto @errors. Later, you can dump them to the screen, to a file, or whatever.

Sorry for the confusion...

Acutally, no, since (as you recall) I want to store the lines of STDERR into an array, not a file.

   $SIG{__WARN__} = sub { push @errors, @_; };
[download]