attribute in the queries ?
I'd hazard a bet it's the timeout on the query that's causing you the
problem, if you don't specify a timeout value then CF will be using the
timeout value on the database connection (under advanced settings) and the
query will be timing out, CFSETTING won't even get a look in...
Jb.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 04 December 2003 10:50
To: CF-Talk
Subject: RE: Programatically setting the timeout limit.
Aha !
I've added this as you suggested.
Doesn't seem to make any difference, I still get a "The request has
exceeded the allowable timelimit tag: cfquery" message.
If I set this up in the calling page, do I still need the timeout attribute
in the queries ?
-----Original Message-----
From: John Beynon [mailto:[EMAIL PROTECTED]
Sent: 04 December 2003 10:36
To: CF-Talk
Subject: RE: Programatically setting the timeout limit.
You can use requestimeout= in the URL from the calling page
Jb.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 04 December 2003 10:36
To: CF-Talk
Subject: Programatically setting the timeout limit.
Hello all,
I have a sequence of queries running, each of these are quite large but, at
preset do not time out.
However, when I loop over the first query, then run the second and loop
over that for the third I get one of two error messages:
either a "The request has exceeded the allowable timelimit tag: cfquery" or
The request has exceeded the allowable timelimit tag: cfloop".
I've tried adding :timeout="#CreateTimeSpan(0,0,10,0)#" to the queries
concerned but to no avail.
How do I either programatically alter the administrator settings or even
better set the time out for a cfloop ?
Does anyone have any ideas?
Usually I wouldn't be happy using such large queries but this is for an
internal app that can be run in the background. So timescale is not an
issue.
Cheers,
Darren
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
