> -----Original Message-----
> From: Ken Miller [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 06, 2000 12:13 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [benchmark] DBI/preload (was Re: [RFC] improving memory
> mapping thru code exercising)
>
>
> At 11:10 AM 6/6/00 -0400, Geoffrey Young wrote:
> >
> >
> >> -----Original Message-----
> >> From: Jason Terry [mailto:[EMAIL PROTECTED]]
> >> Sent: Tuesday, June 06, 2000 10:52 AM
> >> To: [EMAIL PROTECTED]
> >> Subject: Re: [benchmark] DBI/preload (was Re: [RFC]
> improving memory
> >> mapping thru code exercising)
> >>
> >>
> >> I just wanted to thank you guys for sending this to the
> mailing list.
> >>
> >> I added these lines to my startup script....
> >> use Carp;
> >> CGI->compile(qw(my_common_functions));
> >> DBI->install_driver('mysql');
>
> I tried this in my startup.pl with Oracle, and this is what I got:
>
> DBI handle cleared whilst still active at
this typically means that you have opened a cursor and the $dbh has gone out
of scope before calling $sth->finish
are you doing other stuff in your startup.pl?
> /home/cardlock/lib/perl5/site_perl/5.005/sun4-solaris/DBD/Orac
> le.pm line 82.
> dbih_clearcom (h 0x54f978, com 0x3319e8):
> FLAGS 0x211: COMSET Warn AutoCommit
> TYPE 1
> PARENT undef
> KIDS 0 (0 active)
> IMP_DATA undef in 'DBD::Oracle::dr'
>
> I tried both
>
> use DBD::Oracle
I use() DBD::Oracle as above in my startup.pl, but I don't see any
warnings...
>
> and
>
> DBI->install_driver( 'Oracle' );
I don't have any experience with this method...
>
> with the same results. It didn't seem to cause any problems, since
> everything still worked.
>
> Something to worry about?
generally no, but since lots of people use() DBD::* in the startup files, it
doesn't sound normal
--GEoff
>
>
> Cheers!
>
> -klm.
>
> -------------------------------------------
> Ken Miller, Consultant
> Shetland Software Services Inc.
>