ColdFusion on knows that an error occurred in that query. The error was
returned to CF from the JDBC drivers which in turn received the error from the
DB server. As I understand it, ColdFusion reported what it was told to report
by a third-party server.
Wil Genovese
Sr. Web Application
: Thursday, June 24, 2010 9:57 PM
To: cf-talk
Subject: Re: Seriously PO'd - cfqueryparam and/or struct dereference flakes
out
It's a bit more code, but if you switch to having a cfargument tag for each
parameter and enforce the type there, you can pass in your struct as an
argument collection. You'll
Have you looked at the datasource to see if there is an issue with the data?
Since you said it worked fine for months.
-Original Message-
From: Marc Funaro [mailto:subscripti...@advantex.net]
Sent: Thursday, June 24, 2010 3:43 PM
To: cf-talk
Subject: Seriously PO'd - cfqueryparam and/or
Thanks everyone,
You were all correct - god help me I was actually focusing on the error CF gave
me, trusting that alone. Go figure. What a rotten thing to do! :)
A different value was the culprit, and the suggestion below absolutely applies.
Thank you all so much -- this is what happens
When CF throws an error on a stored proc, it will usually reference the last
line of the stored proc, not necessarily which line has bad data.
If I were you, I would dump the values that are being sent into the stored proc
and review to see if any of it is null or blank (or string) going into
The line number given is always the last line of the query. Make sure all the
other values are what they are supposed to be.
Wil Genovese
Sr. Web Application Developer/
Systems Administrator
Wil Genovese Consulting
wilg...@trunkful.com
www.trunkful.com
On Jun 24, 2010, at 5:43 PM, Marc
Dump #a# and look at the other values that your query expects to be integers
(a.categoryid and a.imageid). CF only knows your query had an error. The
reported line number when errors fall between cfquery tags is rarely the
line with the actual issue.
.:.:.:.:.:.:.:.:.:.:.:.:.:.
Bobby Hartsfield
It's a bit more code, but if you switch to having a cfargument tag for each
parameter and enforce the type there, you can pass in your struct as an
argument collection. You'll get a more meaningful error that way.
Sent from my HTC on the Now Network from Sprint!
- Reply message -
8 matches
Mail list logo
