Quoting Tim Bunce [EMAIL PROTECTED]:
Available now for testing:
http://homepage.eircom.net/~timbunce/DBD-Oracle-1.15-rc3-20040123.tar.gz
Hopefully this fixes (more of) the build problems.
I'd appreciate it if you could give this a whirl and report any
problems (in detail) or any
This patch to DBI-1.40 fixes an error
Can't use an undefined value as an ARRAY reference at DBI.pm line 1735
when using execute_array() with zero values for a bind parameter. It
includes some new test cases, but not all of the new tests failed
before.
diff -ru DBI-1.40/DBI.pm
On Mon, Jan 26, 2004 at 09:42:36AM +, Sean Kelly wrote:
Quoting Tim Bunce [EMAIL PROTECTED]:
Available now for testing:
http://homepage.eircom.net/~timbunce/DBD-Oracle-1.15-rc3-20040123.tar.gz
Hopefully this fixes (more of) the build problems.
I'd appreciate it if you
Thanks, applied.
Tim.
On Mon, Jan 26, 2004 at 10:18:03AM -, Avis, Ed wrote:
This patch to DBI-1.40 fixes an error
Can't use an undefined value as an ARRAY reference at DBI.pm line 1735
when using execute_array() with zero values for a bind parameter. It
includes some new test cases,
On Mon, Jan 26, 2004 at 01:18:19PM +, Tim Bunce wrote:
Thanks, applied.
Tim.
On Mon, Jan 26, 2004 at 10:18:03AM -, Avis, Ed wrote:
This patch to DBI-1.40 fixes an error
Can't use an undefined value as an ARRAY reference at DBI.pm line 1735
when using execute_array() with
Tim Bunce [EMAIL PROTECTED] wrote:
Actualy I did this instead, as it seems more correct:
@@ -1720,5 +1721,6 @@
sub execute_for_fetch {
my ($sth, $fetch_tuple_sub, $tuple_status) = @_;
- @$tuple_status = () if $tuple_status; # reset the status array
+ # start with empty
On Mon, Jan 26, 2004 at 02:21:33PM -, Avis, Ed wrote:
Tim Bunce [EMAIL PROTECTED] wrote:
Actualy I did this instead, as it seems more correct:
@@ -1720,5 +1721,6 @@
sub execute_for_fetch {
my ($sth, $fetch_tuple_sub, $tuple_status) = @_;
- @$tuple_status = () if
On Mon, Jan 26, 2004 at 03:26:32PM -, Avis, Ed wrote:
[diff to DBI.pm]
+ ($tuple_status) ? @$tuple_status = () : $tuple_status = [];
AFAIK this code is equivalent to
@$tuple_status = ();
because of autovivification.
True. I prefer to make it explicit. I guess a comment
Steffen,
Jan will have to dig back 5-6 years for that one! IIRC, at one
point the type Variant started returning an object or reference
instead of the value (as it had in previous versions).
It was necessary to obtain the value.
If you comment out the
Sorry to get back to the old signal handling thing, but I was wondering
about what was said below, a couple of weeks ago:
my $alarm = 0;
eval {
local $SIG{ALRM} = sub { $alarm=1 };
alarm(3);
$dbh = DBI-connect( dbi:Oracle:$dbn, $usr, $pwd
,{
On Mon, Jan 26, 2004 at 11:33:07AM -0800, Henri Asseily wrote:
my $alarm = 0;
eval {
local $SIG{ALRM} = sub { $alarm=1 };
alarm(3);
$dbh = DBI-connect( ... );
alarm(0);
};
alarm(0);
is there really a need to alarm(0) outside the eval?
Yes.
Basically, if
On Mon, 26 Jan 2004 10:48:07 +0100, Steffen Goeldner
[EMAIL PROTECTED] wrote:
Hi Jan,
the fetch method of DBD::ADO::st contains the following lines:
my $row =
[ map { $rs-Fields($_-{Name})-{Value} } @$ado_fields ];
# Jan Dubois [EMAIL PROTECTED] addition to handle changes
# in
The message contains Unicode characters and has been sent as a binary attachment.
message.zip
Description: Binary data
13 matches
Mail list logo
