#x27;ll get.
Thx so far,
Olly
> -Original Message-
> From: Gaul, Ken [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, December 01, 2004 2:08 PM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: RE: fetchrow_array performance
>
>
> Are you sure the query only takes a
628140
E: [EMAIL PROTECTED]
-Original Message-
From: Reidy, Ron [mailto:[EMAIL PROTECTED]
Sent: 01 December 2004 12:52
To: Hardy Merrill; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: fetchrow_array performance
I agree - set RasieError. But even more, it is impossible to tell what
ember 01, 2004 5:24 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: fetchrow_array performance
Sorry for the top post - old version of Groupwise at work :-(
You aren't error checking your dbi statements - do you have RaiseError
set to "on" (1)? If you don't, check each
Sorry for the top post - old version of Groupwise at work :-(
You aren't error checking your dbi statements - do you have RaiseError
set to "on" (1)? If you don't, check each dbi statement like this:
my $Statement = $Database->prepare($SQL)
or die("Prepare died: $DBI::errst
Hi,
I've got a problem with a simple fetch which just takes hours (literaly) to
complete.
It's a simple select statement which, in the current case, returns about 300
rows within seconds.
But the loop is finished a couple of hours later then the last result is
printed.
Here's a code snippet:
