Re: [DBI] RE: Correct way to deal with returned NULLs?
From: Dave Cash (dave_at_gnofn.org)
Date: 04/26/04
- Previous message: Rich Jesse: "RE: Correct way to deal with returned NULLs?"
- In reply to: Rich Jesse: "RE: Correct way to deal with returned NULLs?"
- Next in thread: Lincoln A. Baxter: "Re: Correct way to deal with returned NULLs?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 26 Apr 2004 12:42:58 -0500 (CDT) To: "Jesse, Rich" <Rich.Jesse@quadtechworld.com>
On Mon, 26 Apr 2004, Jesse, Rich wrote:
> Thanks all for your responses. We went with Michael's answer for this
> project, although I'd probably advocate the others that checked for
> "defined" for the future.
In the spirit of TMTOWTDI...
I'm not sure, but I think the following is equivalent to Michael's
solution:
use warnings;
no warnings qw(uninitialized);
Not sure what version of Perl you're using, but this is a good read
on warnings (from the 5.8.0 docs):
http://www.perldoc.com/perl5.8.0/pod/perllexwarn.html
Take care,
Dave
> Thanks again!
> Rich
>
> Rich Jesse System/Database Administrator
> rich.jesse@quadtechworld.com QuadTech, Sussex, WI USA
>
>
> > -----Original Message-----
> > From: Michael Ragsdale [mailto:mragsdal@utk.edu]
> > Sent: Monday, April 26, 2004 10:29 AM
> > To: Jesse, Rich
> > Subject: Re: Correct way to deal with returned NULLs?
> >
> >
> > You can place the following near the beginning of your script
> > to eliminate
> > those messages:
> >
> > $SIG{__WARN__} = sub { warn $_[0] unless $_[0] =~
> > /uninitialized value/ };
- Previous message: Rich Jesse: "RE: Correct way to deal with returned NULLs?"
- In reply to: Rich Jesse: "RE: Correct way to deal with returned NULLs?"
- Next in thread: Lincoln A. Baxter: "Re: Correct way to deal with returned NULLs?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
