On Tue 13 Jan 2004 15:42, Tim Bunce <[EMAIL PROTECTED]> wrote:
> On Mon, Jan 12, 2004 at 04:59:38PM +0100, H.Merijn Brand wrote:
> >
> > > B. What changes you'd like to see in the DBD API
> > > (that's the DBI<->DBD interface).
> >
> > � All dbh handel offspring (statement handles and such)
> > available from the top level handle, for both status
> > and cleanup purposes
>
> Yeap. A weakref cache is on the list.
Good!
> > � Generic (DBI level) possibility to enable DBD debugging
> > I enabled $dbh->{DBDverbose}, to be the DBD counterpart
> > of DBI::trace (), and later renamed that - on Tim's
> > request - to $dbh->{uni_verbose}, but IMHO the usefulness
> > warrants a high level attribute
>
> A reorg of how TraceLevel works is on the list. You may remember me
> posting about that some months ago. Having an 8bit (max) trace level
> and then 16bits for specific topics and 8bits spare for driver topics.
I remember, but I wanted to stress this. It's important for me (and my
misbehaving database drivers - DBI and DBD do OK)
Example:
bug report: I cannot open blahdieblah, because I get an
undocumented error -273
answer: That seems to be a programming error. In this
case you can ignore it
> Tim.
--
H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/)
using perl-5.6.1, 5.8.0 & 633 on HP-UX 10.20 & 11.00, AIX 4.2, AIX 4.3,
WinNT 4, Win2K pro & WinCE 2.11 often with Tk800.024 &/| DBD-Unify
ftp://ftp.funet.fi/pub/languages/perl/CPAN/authors/id/H/HM/HMBRAND/
