Re: Announce: DBI 1.38 release candidate
Great. I'm glad that mystery is solved. Thanks.
Tim.
On Fri, Aug 29, 2003 at 05:06:12PM +0200, H.Merijn Brand wrote:
On Fri 29 Aug 2003 16:49, Tim Bunce [EMAIL PROTECTED] wrote:
On Fri, Aug 29, 2003 at 02:29:40PM +0200, H.Merijn Brand wrote:
On Thu 28 Aug 2003 20:59, Tim Bunce [EMAIL PROTECTED] wrote:
On Thu, Aug 28, 2003 at 02:40:46PM +0200, H.Merijn Brand wrote:
One of the reasons I'm still holding on to DBI-1.35 is
Argument isn't numeric in null operation at
/pro/lib/perl5/site_perl/5.8.0/PA-RISC2.0/DBI.pm line 632.
which is caused by attr 'Username' which is either undef or blank
I suspect the problem is in DBD::Unify. Does it happen for any other DBD's?
a5:/pro/3gl/CPAN/DBD-Unify-0.27 102 grep Username *
a5:/pro/3gl/CPAN/DBD-Unify-0.27 103 grep Username */*
I'm not sure why you're showing me greps. I think the problem is
To show that *I* am/was not using the Username attribute :)
that DBD::Unify STORE is stringifying the value.
Hang on... [wanders over to
http://search.cpan.org/src/HMBRAND/DBD-Unify-0.26/dbdimp.ic]
yes, your dbd_db_STORE_attrib function is doing
int on = SvIV (valuesv);
instead of
int on = SvTRUE(valuesv);
I can assure you I did not invent that line myself :) It was blindly copied
from some other DBD driver, as stated in the header:
* Main sources were Oracle (1.03), FreeTDS (0.02) and Ingres (0.24, 0.25)
* whose writers seem to have copied from other sources too ;-)
[ Wanders over to Oracle-1.03 ...
lep a5:/pro/3gl/CPAN/DBD-Oracle-1.03 115 grep -w on * | grep Sv
dbdimp.c:int on = SvTRUE(valuesv);
dbdimp.c:int on = SvTRUE(valuesv);
lep a5:/pro/3gl/CPAN/DBD-Oracle-1.03 116
Hmm, no that's OK ... Wanders to FreeTDS ...
lep a5:/pro/3gl/CPAN 119 grep -rw on DBD-FreeTDS-0.02 | grep Sv
Exit 1
lep a5:/pro/3gl/CPAN 120
Hmm checking Ingres ...
lep a5:/pro/3gl/CPAN 123 grep -rw on DBD-Ingres-0.25 | grep Sv
DBD-Ingres-0.25/dbdimp.psc:int on = SvTRUE(valuesv);
DBD-Ingres-0.25/dbdimp.psc:int on = SvTRUE(valuesv);
lep a5:/pro/3gl/CPAN 124
By then I was by no means an internals guy (and IMHO I'm still not),
so I'm sure I copied it from somewhere ]
Funny that the statement STORE did it right:
int dbd_st_STORE_attrib (SV *sth, imp_sth_t *imp_sth, SV *keysv, SV *valuesv)
{
STRLEN kl;
char *key = SvPV (keysv,kl);
SV *cachesv = NULL;
inton = SvTRUE (valuesv);
I've removed the no warnings again, and changed SvIV () to SvTRUE ()
lep a5:/pro/3gl/CPAN/DBD-Unify-0.27 108 make test
PERL_DL_NONLAZY=1 /pro/bin/perl -MExtUtils::Command::MM -e test_harness(0,
'blib/lib', 'blib/arch') t/*.t
t/01-base.ok
t/02-connect..ok
t/03-general..ok
t/04-long.ok
t/05-reauth...ok
t/10-dbi-drv..ok
t/11-dbi-dbh..ok
t/12-dbi-sth..ok
t/20-uni-basicok
t/21-uni-regexok
t/27-uni-max..ok
t/30-reconnectok
t/99-done.
To disable future max tests: setenv DBD_UNIFY_SKIP_27 1
skipped
all skipped: no reason given
All tests successful, 1 test skipped.
Files=13, Tests=598, 9 wallclock secs ( 7.73 cusr + 0.65 csys = 8.38 CPU)
lep a5:/pro/3gl/CPAN/DBD-Unify-0.27 109
I have rewritten DBD-Unify (with pain in my heart) to replace
$dbh-{DBDverbose} (which IMHO is a perfectly good name, and should be
adopted
by all drivers)
Oh, and I forgot to say: See, I do what I promised in Paris :)
:)
Tim.
--
H.Merijn BrandAmsterdam 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/
Re: Announce: DBI 1.38 release candidate
On Thu 28 Aug 2003 20:59, Tim Bunce [EMAIL PROTECTED] wrote:
On Thu, Aug 28, 2003 at 02:40:46PM +0200, H.Merijn Brand wrote:
One of the reasons I'm still holding on to DBI-1.35 is
Argument isn't numeric in null operation at
/pro/lib/perl5/site_perl/5.8.0/PA-RISC2.0/DBI.pm line 632.
which is caused by attr 'Username' which is either undef or blank
I suspect the problem is in DBD::Unify. Does it happen for any other DBD's?
I don't use the other DBD's very often :)
I don't like Oracle.
a5:/pro/3gl/CPAN/DBD-Unify-0.27 102 grep Username *
Exit 1
a5:/pro/3gl/CPAN/DBD-Unify-0.27 103 grep Username */*
Binary file ulib/unify.cmf matches
ulib/unify.msg: 8889|Username :
ulib/unify.msg: 8959!Invalid Username/Password. (#)
ulib/unify.msg: 8964|usage: %s [Username[/Password]]
ulib/unify.msg: 15889|Username:
ulib/unify.msg: 15964|usage: %s [Username[/Password]]
a5:/pro/3gl/CPAN/DBD-Unify-0.27 104
for now, I've changed that to
foreach $a (keys %$attr) {
no warnings;
$dbh-{$a} = $attr-{$a};
}
so
I have rewritten DBD-Unify (with pain in my heart) to replace
$dbh-{DBDverbose} (which IMHO is a perfectly good name, and should be adopted
by all drivers)
Oh, and I forgot to say: See, I do what I promised in Paris :)
I have vague plans to turn the high bits of the trace level into a
bit mask to enable some specific trace features. In other words, use
the lowest 8 bits for current general use, the next 8 bits for a DBD
specific trace level, and the next 16 bits for special features.
Patches welcome! :)
Yeah! (to be honoust, I used it the other way round in user scripts, because
I'm usually more interested in what happens in the DBD, than what happens in
the DBI. The DBI usually kinda `behaves')
to $dbh-{uni_verbose} as the documentation requires.
That works, but I'd like to have one intermediate release that warns if
DBDverbose is in use. What would be the best place to do so?
Er, I'm not sure what you mean but I'd suggest the STORE that handles
the setting of the DBDverbose attribute.
Yep, I've already caught these, but can I hijack the DBI level, because
$dbh-{DBDverbose} will not get through anymore
My DBD's depend on my environment, so here's the same thing twice
Thanks.
Still searching for time to extend DBD::Unify, though this change might be
just enough reason to start catching up ...
--
H.Merijn BrandAmsterdam 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/
Re: Announce: DBI 1.38 release candidate
On Fri, Aug 29, 2003 at 02:29:40PM +0200, H.Merijn Brand wrote:
On Thu 28 Aug 2003 20:59, Tim Bunce [EMAIL PROTECTED] wrote:
On Thu, Aug 28, 2003 at 02:40:46PM +0200, H.Merijn Brand wrote:
One of the reasons I'm still holding on to DBI-1.35 is
Argument isn't numeric in null operation at
/pro/lib/perl5/site_perl/5.8.0/PA-RISC2.0/DBI.pm line 632.
which is caused by attr 'Username' which is either undef or blank
I suspect the problem is in DBD::Unify. Does it happen for any other DBD's?
a5:/pro/3gl/CPAN/DBD-Unify-0.27 102 grep Username *
a5:/pro/3gl/CPAN/DBD-Unify-0.27 103 grep Username */*
I'm not sure why you're showing me greps. I think the problem is
that DBD::Unify STORE is stringifying the value.
Hang on... [wanders over to
http://search.cpan.org/src/HMBRAND/DBD-Unify-0.26/dbdimp.ic]
yes, your dbd_db_STORE_attrib function is doing
int on = SvIV (valuesv);
instead of
int on = SvTRUE(valuesv);
I have rewritten DBD-Unify (with pain in my heart) to replace
$dbh-{DBDverbose} (which IMHO is a perfectly good name, and should be adopted
by all drivers)
Oh, and I forgot to say: See, I do what I promised in Paris :)
:)
Tim.
Re: Announce: DBI 1.38 release candidate
On Fri 29 Aug 2003 16:49, Tim Bunce [EMAIL PROTECTED] wrote:
On Fri, Aug 29, 2003 at 02:29:40PM +0200, H.Merijn Brand wrote:
On Thu 28 Aug 2003 20:59, Tim Bunce [EMAIL PROTECTED] wrote:
On Thu, Aug 28, 2003 at 02:40:46PM +0200, H.Merijn Brand wrote:
One of the reasons I'm still holding on to DBI-1.35 is
Argument isn't numeric in null operation at
/pro/lib/perl5/site_perl/5.8.0/PA-RISC2.0/DBI.pm line 632.
which is caused by attr 'Username' which is either undef or blank
I suspect the problem is in DBD::Unify. Does it happen for any other DBD's?
a5:/pro/3gl/CPAN/DBD-Unify-0.27 102 grep Username *
a5:/pro/3gl/CPAN/DBD-Unify-0.27 103 grep Username */*
I'm not sure why you're showing me greps. I think the problem is
To show that *I* am/was not using the Username attribute :)
that DBD::Unify STORE is stringifying the value.
Hang on... [wanders over to
http://search.cpan.org/src/HMBRAND/DBD-Unify-0.26/dbdimp.ic]
yes, your dbd_db_STORE_attrib function is doing
int on = SvIV (valuesv);
instead of
int on = SvTRUE(valuesv);
I can assure you I did not invent that line myself :) It was blindly copied
from some other DBD driver, as stated in the header:
* Main sources were Oracle (1.03), FreeTDS (0.02) and Ingres (0.24, 0.25)
* whose writers seem to have copied from other sources too ;-)
[ Wanders over to Oracle-1.03 ...
lep a5:/pro/3gl/CPAN/DBD-Oracle-1.03 115 grep -w on * | grep Sv
dbdimp.c:int on = SvTRUE(valuesv);
dbdimp.c:int on = SvTRUE(valuesv);
lep a5:/pro/3gl/CPAN/DBD-Oracle-1.03 116
Hmm, no that's OK ... Wanders to FreeTDS ...
lep a5:/pro/3gl/CPAN 119 grep -rw on DBD-FreeTDS-0.02 | grep Sv
Exit 1
lep a5:/pro/3gl/CPAN 120
Hmm checking Ingres ...
lep a5:/pro/3gl/CPAN 123 grep -rw on DBD-Ingres-0.25 | grep Sv
DBD-Ingres-0.25/dbdimp.psc:int on = SvTRUE(valuesv);
DBD-Ingres-0.25/dbdimp.psc:int on = SvTRUE(valuesv);
lep a5:/pro/3gl/CPAN 124
By then I was by no means an internals guy (and IMHO I'm still not),
so I'm sure I copied it from somewhere ]
Funny that the statement STORE did it right:
int dbd_st_STORE_attrib (SV *sth, imp_sth_t *imp_sth, SV *keysv, SV *valuesv)
{
STRLEN kl;
char *key = SvPV (keysv,kl);
SV *cachesv = NULL;
inton = SvTRUE (valuesv);
I've removed the no warnings again, and changed SvIV () to SvTRUE ()
lep a5:/pro/3gl/CPAN/DBD-Unify-0.27 108 make test
PERL_DL_NONLAZY=1 /pro/bin/perl -MExtUtils::Command::MM -e test_harness(0,
'blib/lib', 'blib/arch') t/*.t
t/01-base.ok
t/02-connect..ok
t/03-general..ok
t/04-long.ok
t/05-reauth...ok
t/10-dbi-drv..ok
t/11-dbi-dbh..ok
t/12-dbi-sth..ok
t/20-uni-basicok
t/21-uni-regexok
t/27-uni-max..ok
t/30-reconnectok
t/99-done.
To disable future max tests: setenv DBD_UNIFY_SKIP_27 1
skipped
all skipped: no reason given
All tests successful, 1 test skipped.
Files=13, Tests=598, 9 wallclock secs ( 7.73 cusr + 0.65 csys = 8.38 CPU)
lep a5:/pro/3gl/CPAN/DBD-Unify-0.27 109
I have rewritten DBD-Unify (with pain in my heart) to replace
$dbh-{DBDverbose} (which IMHO is a perfectly good name, and should be adopted
by all drivers)
Oh, and I forgot to say: See, I do what I promised in Paris :)
:)
Tim.
--
H.Merijn BrandAmsterdam 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/
Re: Announce: DBI 1.38 release candidate
On Thu 21 Aug 2003 19:31, Thomas A. Lowery [EMAIL PROTECTED] wrote:
All tests successful, 6 tests skipped.
Files=34, Tests=1372, 84 wallclock secs (70.24 cusr + 4.02 csys = 74.26 CPU)
Perl: 5.008
OS : linux
DBI : 1.38
DBD::mysql : 2.1021
DBD::Sponge : 11.09
DBD::Proxy : 0.2004
DBD::Pg : 1.31_3
DBD::Oracle : 1.14
DBD::Multiplex : 0.9
DBD::File : 0.2001
DBD::ExampleP : 11.10
DBD::CSV: 0.2002
Original request got lost in Sobig
This is a *very* recent 5.8.x snapshot (20906) built with gcc-3.3.1/64
h3:/u/usr/merijn 101 /opt/perl64/bin/perl -MDBI -e 'DBI-installed_versions'
Perl: 5.008001(PA-RISC2.0-LP64)
OS : hpux(11.11)
DBI : 1.38
DBD::Sponge : 11.09
DBD::Proxy : install_driver(Proxy) failed: Can't locate RPC/PlClient.pm in @INC
DBD::File : 0.2001
DBD::ExampleP : 11.10
DBD::CSV: 0.2002
h3:/u/usr/merijn 102
One of the reasons I'm still holding on to DBI-1.35 is
Argument isn't numeric in null operation at
/pro/lib/perl5/site_perl/5.8.0/PA-RISC2.0/DBI.pm line 632.
which is caused by attr 'Username' which is either undef or blank
t/27-uni-max..$VAR1 = {
'Username' = undef
};
Use of uninitialized value in null operation at
/pro/lib/perl5/site_perl/5.8.0/PA-RISC2.0/DBI.pm line 633.
t/27-uni-max..ok
t/30-reconnect$VAR1 = {
'Username' = ''
};
Argument isn't numeric in null operation at
/pro/lib/perl5/site_perl/5.8.0/PA-RISC2.0/DBI.pm line 633.
t/30-reconnectok 4/9$VAR1 = {
'Username' = ''
};
Argument isn't numeric in null operation at
/pro/lib/perl5/site_perl/5.8.0/PA-RISC2.0/DBI.pm line 633.
t/30-reconnectok
for now, I've changed that to
foreach $a (keys %$attr) {
no warnings;
$dbh-{$a} = $attr-{$a};
}
so
I have rewritten DBD-Unify (with pain in my heart) to replace
$dbh-{DBDverbose} (which IMHO is a perfectly good name, and should be adopted
by all drivers) to $dbh-{uni_verbose} as the documentation requires.
That works, but I'd like to have one intermediate release that warns if
DBDverbose is in use. What would be the best place to do so?
My DBD's depend on my environment, so here's the same thing twice
lep a5:/pro/3gl/CPAN/DBD-Unify-0.25 111 perl -MDBI -e 'DBI-installed_versions'
Perl: 5.008 (PA-RISC2.0)
OS : hpux(11.00)
DBI : 1.38
DBD::Unify : 0.25
DBD::Sponge : 11.09
DBD::Proxy : install_driver(Proxy) failed: Can't locate RPC/PlClient.pm in @INC
DBD::File : 0.2001
DBD::ExampleP : 11.10
DBD::CSV: 0.2002
lep a5:/pro/3gl/CPAN/DBD-Unify-0.25 112
lep a5:/pro/to/lep/4gl 101 perl -MDBI -e 'DBI-installed_versions'
Perl: 5.008 (PA-RISC2.0)
OS : hpux(11.00)
DBI : 1.38
DBD::Sponge : 11.09
DBD::Proxy : install_driver(Proxy) failed: Can't locate RPC/PlClient.pm in @INC
DBD::Oracle : 1.14
DBD::File : 0.2001
DBD::ExampleP : 11.10
DBD::CSV: 0.2002
lep a5:/pro/to/lep/4gl 102
--
H.Merijn BrandAmsterdam 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/
Re: Announce: DBI 1.38 release candidate
On Thu, Aug 28, 2003 at 02:40:46PM +0200, H.Merijn Brand wrote:
One of the reasons I'm still holding on to DBI-1.35 is
Argument isn't numeric in null operation at
/pro/lib/perl5/site_perl/5.8.0/PA-RISC2.0/DBI.pm line 632.
which is caused by attr 'Username' which is either undef or blank
I suspect the problem is in DBD::Unify. Does it happen for any other DBD's?
for now, I've changed that to
foreach $a (keys %$attr) {
no warnings;
$dbh-{$a} = $attr-{$a};
}
so
I have rewritten DBD-Unify (with pain in my heart) to replace
$dbh-{DBDverbose} (which IMHO is a perfectly good name, and should be adopted
by all drivers)
I have vague plans to turn the high bits of the trace level into a
bit mask to enable some specific trace features. In other words, use
the lowest 8 bits for current general use, the next 8 bits for a DBD
specific trace level, and the next 16 bits for special features.
Patches welcome! :)
to $dbh-{uni_verbose} as the documentation requires.
That works, but I'd like to have one intermediate release that warns if
DBDverbose is in use. What would be the best place to do so?
Er, I'm not sure what you mean but I'd suggest the STORE that handles
the setting of the DBDverbose attribute.
My DBD's depend on my environment, so here's the same thing twice
Thanks.
Tim.
Re: Announce: DBI 1.38 release candidate
On Wed, Aug 20, 2003 at 03:52:26PM -0700, David Wheeler wrote: Oh yeah, I meant to leave those out. I've gotten used to ignoring those warnings. It's just the `Perl___notused' warnings I wanted to draw attention to. They're a perl implementation detail that's hard to avoid. Tim.
Re: Announce: DBI 1.38 release candidate
Tim Bunce wrote: [...] If all is well please reply to the list with a short message giving the output of: perl -MDBI -e 'DBI-installed_versions' Perl: 5.006001 OS : MSWin32 DBI : 1.38 DBD::Sponge : 11.09 DBD::Oracle : 1.14 DBD::ODBC : 1.05 DBD::Multiplex : 0.2 DBD::ExampleP : 11.10 DBD::ADO: 2.6 Steffen
Re: Announce: DBI 1.38 release candidate
Tim Bunce wrote: I'd be grateful if you could take a moment to try out this release candidate of DBI 1.38: All tests successful, 9 tests skipped. Files=34, Tests=1215, 33 wallclock secs ( 9.09 cusr + 0.67 csys = 9.76 CPU) $perl -MDBI -e 'DBI-installed_versions' Perl: 5.006001 OS : linux DBI : 1.38 DBD::Sybase : 0.95 DBD::Sponge : 11.09 DBD::Pg : 1.22 DBD::ODBC : 1.05 DBD::LDAP : 0.05 DBD::Informix : 1.00.PC2 DBD::File : 0.1023 DBD::Excel : 0.05 DBD::ExampleP : 11.10 DBD::DB2: 0.76 DBD::CSV: 0.1030 -- Cosimo WinNT error 003: FPU error - enter any 11 digit prime number to continue.
Re: Announce: DBI 1.38 release candidate
d On 20-Aug-2003 Tim Bunce wrote: On Wed, Aug 20, 2003 at 09:02:21AM -0700, David Wheeler wrote: On Wednesday, August 20, 2003, at 07:49 AM, Tim Bunce wrote: I'd be grateful if you could take a moment to try out this release candidate of DBI 1.38: scotthperl -Mblib -MDBI -e 'DBI-installed_versions' Using /usr/home/shildret/src/DBI/DBI-1.38/blib Perl: 5.006001 OS : freebsd DBI : 1.38 DBD::mysql : 2.9002 DBD::XBase : 0.210 DBD::Sponge : 11.09 DBD::SQLite : 0.25 DBD::Proxy : 0.2004 DBD::Oracle : 1.14 DBD::Multiplex : 0.9 DBD::File : 0.1022 DBD::ExampleP : 11.10 DBD::CSV: 0.1027 DBD::AnyData: 0.05 -- E-Mail: [EMAIL PROTECTED] Date: 21-Aug-2003 Time: 08:13:12 --
Re: Announce: DBI 1.38 release candidate
On Thursday, August 21, 2003, at 02:03 AM, Tim Bunce wrote: Oh yeah, I meant to leave those out. I've gotten used to ignoring those warnings. It's just the `Perl___notused' warnings I wanted to draw attention to. They're a perl implementation detail that's hard to avoid. Ah, okay, as long as there's no harm. I'll look at upgrading to gcc 3.3. Regards. David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://www.kineticode.com/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED] Kineticode. Setting knowledge in motion.[sm]
Re: Announce: DBI 1.38 release candidate
and... scotthperl -Mblib -MDBI -e 'DBI-installed_versions' Perl: 5.008001 OS : freebsd DBI : 1.38 DBD::mysql : 2.9002 DBD::Sponge : 11.09 DBD::SQLite : 0.25 DBD::Proxy : 0.2004 DBD::Oracle : 1.14 DBD::ExampleP : 11.10 On 21-Aug-2003 [EMAIL PROTECTED] wrote: d On 20-Aug-2003 Tim Bunce wrote: On Wed, Aug 20, 2003 at 09:02:21AM -0700, David Wheeler wrote: On Wednesday, August 20, 2003, at 07:49 AM, Tim Bunce wrote: I'd be grateful if you could take a moment to try out this release candidate of DBI 1.38: scotthperl -Mblib -MDBI -e 'DBI-installed_versions' Using /usr/home/shildret/src/DBI/DBI-1.38/blib Perl: 5.006001 OS : freebsd DBI : 1.38 DBD::mysql : 2.9002 DBD::XBase : 0.210 DBD::Sponge : 11.09 DBD::SQLite : 0.25 DBD::Proxy : 0.2004 DBD::Oracle : 1.14 DBD::Multiplex : 0.9 DBD::File : 0.1022 DBD::ExampleP : 11.10 DBD::CSV: 0.1027 DBD::AnyData: 0.05 -- E-Mail: [EMAIL PROTECTED] Date: 21-Aug-2003 Time: 08:13:12 -- -- E-Mail: [EMAIL PROTECTED] Date: 21-Aug-2003 Time: 11:35:24 --
Re: Announce: DBI 1.38 release candidate
All tests successful, 6 tests skipped. Files=34, Tests=1372, 84 wallclock secs (70.24 cusr + 4.02 csys = 74.26 CPU) Perl: 5.008 OS : linux DBI : 1.38 DBD::mysql : 2.1021 DBD::Sponge : 11.09 DBD::Proxy : 0.2004 DBD::Pg : 1.31_3 DBD::Oracle : 1.14 DBD::Multiplex : 0.9 DBD::File : 0.2001 DBD::ExampleP : 11.10 DBD::CSV: 0.2002
Re: Announce: DBI 1.38 release candidate
On Wednesday, August 20, 2003, at 07:49 AM, Tim Bunce wrote: I'd be grateful if you could take a moment to try out this release candidate of DBI 1.38: All tests passed for me. mercury% perl -MDBI -e 'DBI-installed_versions' Perl: 5.008 OS : darwin DBI : 1.38 DBD::Sponge : 11.09 DBD::Pg : 1.31_2 DBD::ExampleP : 11.10 I did get a lot of warnings during `make`, though: DBI.xs: In function `dbih_clearcom': DBI.xs:977: warning: unused variable `Perl___notused' DBI.xs: In function `dbih_get_fbav': DBI.xs:1114: warning: unused variable `Perl___notused' DBI.xs: In function `dbih_set_attr_k': DBI.xs:1269: warning: unused variable `Perl___notused' DBI.xs:1194: warning: unused variable `Perl___notused' DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.xs: In function `dbih_get_attr_k': DBI.xs:1405: warning: unused variable `Perl___notused' DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.xs: In function `log_where': DBI.xs:1782: warning: unused variable `Perl___notused' DBI.xs: In function `XS_DBI_dispatch': DBI.xs:2542: warning: unused variable `Perl___notused' DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.xs: In function `preparse': DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.c: In function `XS_DBI__handles': DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.c: In function `XS_DBI_dump_handle': DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.c: In function `XS_DBI_dbi_profile': DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.c: In function `XS_DBD_db_take_imp_data': DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.c: In function `XS_DBD_st__set_fbav': DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.c: In function `XS_DBD_st_bind_columns': DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.c: In function `XS_DBD_st_fetchrow_array': DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.c: In function `XS_DBD_st_fetchrow_hashref': DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.c: In function `XS_DBD_st_fetch': DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.c: In function `XS_DBD_st_finish': DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.c: In function `XS_DBD_common_errstr': DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.c: In function `XS_DBD_common_set_err': DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.c: In function `XS_DBD_common_trace': DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.c: In function `XS_DBI__get_imp_data': DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.c: In function `XS_DBD_st__get_fbav': DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.c: In function `XS_DBD_st_rows': DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.c: In function `XS_DBD_common_private_data': DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.c: In function `XS_DBD_common_err': DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.c: In function `XS_DBD_common_state': DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.c: In function `dbih_setup_handle': DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.c: In function `dbih_sth_bind_col': DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.c: In function `dbih_getcom': DBI.xs:610: warning: `sv' might be used uninitialized in this function DBI.c: In function `dbih_make_com': DBI.xs:720: warning: `memzero_size' might be used uninitialized in this function DBI.c: In function `dbih_make_fdsv': DBI.xs:610: warning: `sv' might be used uninitialized in this function Regards, David -- David Wheeler AIM: dwTheory
Re: Announce: DBI 1.38 release candidate
On Wed, Aug 20, 2003 at 09:02:21AM -0700, David Wheeler wrote:
On Wednesday, August 20, 2003, at 07:49 AM, Tim Bunce wrote:
I'd be grateful if you could take a moment to try out this
release candidate of DBI 1.38:
All tests passed for me.
mercury% perl -MDBI -e 'DBI-installed_versions'
Perl: 5.008
OS : darwin
DBI : 1.38
DBD::Sponge : 11.09
DBD::Pg : 1.31_2
DBD::ExampleP : 11.10
I did get a lot of warnings during `make`, though:
DBI.xs:610: warning: `sv' might be used uninitialized in this function
Thanks. Does this fix those?
--- DBI.xs 2003/08/20 00:15:24 11.31
+++ DBI.xs 2003/08/20 21:19:52
@@ -617,6 +617,7 @@
else {
sv_dump(hrv);
croak(Invalid DBI handle %s, neatsvpv(hrv,0));
+ sv = sv_undef; /* avoid might be used uninitialized warning */
}
/* Short cut for common case. We assume that a magic var always*/
Tim.
Re: Announce: DBI 1.38 release candidate
On Wednesday, August 20, 2003, at 02:20 PM, Tim Bunce wrote:
All tests passed for me.
mercury% perl -MDBI -e 'DBI-installed_versions'
Perl: 5.008
OS : darwin
DBI : 1.38
DBD::Sponge : 11.09
DBD::Pg : 1.31_2
DBD::ExampleP : 11.10
I did get a lot of warnings during `make`, though:
DBI.xs:610: warning: `sv' might be used uninitialized in this function
Thanks. Does this fix those?
--- DBI.xs 2003/08/20 00:15:24 11.31
+++ DBI.xs 2003/08/20 21:19:52
@@ -617,6 +617,7 @@
else {
sv_dump(hrv);
croak(Invalid DBI handle %s, neatsvpv(hrv,0));
+ sv = sv_undef; /* avoid might be used uninitialized warning
*/
}
/* Short cut for common case. We assume that a magic var always
*/
Yes, but there are still the other ones:
cc1: warning: changing search order for system directory
/usr/local/include
cc1: warning: as it has already been specified as a non-system
directory
DBI.xs: In function `dbih_clearcom':
DBI.xs:978: warning: unused variable `Perl___notused'
DBI.xs: In function `dbih_get_fbav':
DBI.xs:1115: warning: unused variable `Perl___notused'
DBI.xs: In function `dbih_set_attr_k':
DBI.xs:1270: warning: unused variable `Perl___notused'
DBI.xs:1195: warning: unused variable `Perl___notused'
DBI.xs: In function `dbih_get_attr_k':
DBI.xs:1406: warning: unused variable `Perl___notused'
DBI.xs: In function `log_where':
DBI.xs:1783: warning: unused variable `Perl___notused'
DBI.xs: In function `XS_DBI_dispatch':
DBI.xs:2543: warning: unused variable `Perl___notused'
DBI.c: In function `dbih_make_com':
DBI.xs:721: warning: `memzero_size' might be used uninitialized in this
function
Regards,
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://www.kineticode.com/ Yahoo!: dew7e
Jabber: [EMAIL PROTECTED]
Kineticode. Setting knowledge in motion.[sm]
Re: Announce: DBI 1.38 release candidate
On Wednesday, August 20, 2003, at 03:44 PM, Bjoern Kriews wrote: On Wednesday, August 20, 2003, at 11:45 PM, David Wheeler wrote: Yes, but there are still the other ones: cc1: warning: changing search order for system directory /usr/local/include cc1: warning: as it has already been specified as a non-system directory DBI.xs: In function `dbih_clearcom': DBI.xs:978: warning: unused variable `Perl___notused' wrt the include warning: I assume you have perl in /usr/local ? Apples gcc is nitpicking here but is has a point about search order. Oh yeah, I meant to leave those out. I've gotten used to ignoring those warnings. It's just the `Perl___notused' warnings I wanted to draw attention to. wrt the other warnings: I use apples gcc-3.3 (available on developer.apple.com after free reg) and I don't see any warnings (but I am not in /usr/local). Ah, I have 3.1. I guess I need to download the latest Developer package. I thought 3.3 was only on Panther, though... Regards, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://www.kineticode.com/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED] Kineticode. Setting knowledge in motion.[sm]
Re: Announce: DBI 1.38 release candidate
On Wednesday, August 20, 2003, at 11:45 PM, David Wheeler wrote: Yes, but there are still the other ones: cc1: warning: changing search order for system directory /usr/local/include cc1: warning: as it has already been specified as a non-system directory DBI.xs: In function `dbih_clearcom': DBI.xs:978: warning: unused variable `Perl___notused' wrt the include warning: I assume you have perl in /usr/local ? Apples gcc is nitpicking here but is has a point about search order. wrt the other warnings: I use apples gcc-3.3 (available on developer.apple.com after free reg) and I don't see any warnings (but I am not in /usr/local). Regards, Bjoern
Re: Announce: DBI 1.38 release candidate
On Wednesday, August 20, 2003, at 4:49 PM, Tim Bunce wrote: I'd be grateful if you could take a moment to try out this release candidate of DBI 1.38: http://homepage.eircom.net/~timbunce/DBI-1.38-rc1-20030820.tar.gz Tim, thanks for including the HandleError stuff. For the list: It was an esoteric problem when there was a readonly return value (i.e. undef) in outitems when you were trying to manipulate it in a HandleError sub. Tim fixed it to check for that and sv2_mortal() it if required. perl -MDBI -e 'DBI-installed_versions' Perl: 5.008001 (RC2, threaded) OS : darwin DBI : 1.38 DBD::mysql : 2.9002 DBD::Sponge : 11.09 DBD::ExampleP : 11.10 All tests passed. DBD::mysql complains about do and rows being doubly defined in mysql.xs which I think it didn't do with 1.37 but I will verify this with a possibly newer version tomorrow - this one doesn't pass all tests against mysql 4.1.0 anyway. I will feed it to a bunch of coworkers on our heavily used test environment. Regards, Bjoern
