John Trammell wrote:
#!perl
use strict;
use warnings;
sub foo {
warn "wantarray() in foo() is: ", wantarray(), "\n";
my @r = 3 .. 8;
return @r;
}
my @x = foo() or warn "in ... or warn() #1\n";
warn "[EMAIL PROTECTED]: @x\n";
my $x = foo() or warn "in ... or warn() #2\n";
warn "\$
"in ... or warn() #2\n";
warn "\$x: $x\n";
> -Original Message-
> From: Michael Stassen [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 21, 2005 12:48 PM
> To: olly@lfix.co.uk
> Cc: debian-user@lists.debian.org; mysql@lists.mysql.com
> Subject: Re: Sarge problem
Oliver Elphick wrote:
We have an application that has just upgraded to Debian sarge with mysql
upgrading from 3.23.49 to 4.0.24. As far as I know I have followed all
the procedures for upgrading the database.
Some queries always fail in DBD::mysql (in DBI) although they work OK
with the mysql
Oliver Elphick wrote:
>which returns 0 rows, works correctly in mysql. But when it is passed
>through this statement in Perl:
>
>my @row = $dbh->selectrow_array($sql) or
>&failed(__FILE__, __LINE__,
> "Failed to run the sql statement with error
>
We have an application that has just upgraded to Debian sarge with mysql
upgrading from 3.23.49 to 4.0.24. As far as I know I have followed all
the procedures for upgrading the database.
Some queries always fail in DBD::mysql (in DBI) although they work OK
with the mysql client.
For example, thi
> I'm having a problem opening the data source of the MySQL
> server. The set
> up of my servers are as follows:
>
> 1. My remote server is a Unix Apache and is with an ISP. I've
> installed/unzipped the Data-Dumper, DBI, MSQL-MySQL Module and the
> CGI.pm into a folder just off the root. I n
I'm having a problem opening the data source of the MySQL server. The set
up of my servers are as follows:
1. My remote server is a Unix Apache and is with an ISP. I've
installed/unzipped the Data-Dumper, DBI, MSQL-MySQL Module and the
CGI.pm into a folder just off the root. I named the folder
7 matches
Mail list logo
