On Tue, Mar 30, 2004 at 08:29:27AM -0500, [EMAIL PROTECTED] wrote: > > I have a lot of code using those methods. I did not realize they were not > standard parts of DBI.
Can you remember what made you think they were? Anybody else out there using them? > What is the alternative mechanism for these methods? $DBI::err, $DBI::errstr, and $DBI::state Tim. > Bob Doucette > > > From: Tim Bunce <[EMAIL PROTECTED]> > > 03/29/2004 06:21 AM > > > > > > To: Dean Arnold <[EMAIL PROTECTED]> > > cc: DBI-users <[EMAIL PROTECTED]> > > Subject: Re: DBI->state() > > > > > > > On Sun, Mar 28, 2004 at 01:56:05PM -0800, Dean Arnold wrote: > > Have the DBI->err(), DBI->errstr(), DBI->state() been > > deprecated ? I see the err() and errstr() are still > > in the DBI.pm code, but no trace of state() (as far > > back as 1.38) > > > > FYI: I'm trying to check state info on a connection > > failure, so I don't have a "handle" to call state() on. > > > > Or is the preferred solution to read the $DBI::state > > variable directly ? > > Yes. DBI->err() and DBI->errstr() were never in the spec > and they'll be removed in DBI v2. > > Tim. > > > >
