On 16/05/11 17:30, Greg Sabino Mullane wrote:
Thanks, Tim, I've adjusted DBD::Pg to throw errors properly.
So have I in DBD::ODBC although I needed to do it in 2 places because of that
bound parameter in Jonathan's example.
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
On 15/05/11 13:08, Jonathan Leffler wrote:
Tested using Perl 5.13.4 and DBI 1.616 now - but I originally spotted the
problem in 2003 when the versions were a lot older...
Consider:
# Test that statement handles from disconnected connections fail!
use strict;
use warnings;
use DBI;
my $table
On Sun, May 15, 2011 at 02:36:51PM -, Greg Sabino Mullane wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Is this a defect in DBI or in DBD::Informix (and NullP)?
Or is it WAD - Working As Designed?
Not sure when this was added, but on DBD::Pg, an error is
given,
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Drivers shouldn't croak() if it can be avoided. The right thing to do is
call set_err_sv() or set_err_char() then return PL_sv_undef (or whatever's
appropriate for an error).
Thanks, Tim, I've adjusted DBD::Pg to throw errors properly.
-
Tested using Perl 5.13.4 and DBI 1.616 now - but I originally spotted the
problem in 2003 when the versions were a lot older...
Consider:
# Test that statement handles from disconnected connections fail!
use strict;
use warnings;
use DBI;
my $table = dbd_tester;
my $dbh =
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Is this a defect in DBI or in DBD::Informix (and NullP)?
Or is it WAD - Working As Designed?
Not sure when this was added, but on DBD::Pg, an error is
given, due to this bit of code in dbdimp.c:
if (NULL == imp_dbh-conn)
croak(execute
On May 15, 2011, at 2:08 PM, Jonathan Leffler wrote:
Tested using Perl 5.13.4 and DBI 1.616 now - but I originally spotted the
problem in 2003 when the versions were a lot older...
Consider:
# Test that statement handles from disconnected connections fail!
use strict;
use warnings;
