Query columns = CF Objects

I spent about 30 minutes this morning tracking down a bug. For the life of me I could not see what the problem was. I had a asynchronous event throwing an error and the error in the logs stated there was an error invoking the event gateway. However, due to the way that CF logs errors the message, however accurate, did not give very much detail as to where the error actually occurred. So, I turned on my custom debugging for gateways that I wrote and was able to track down the error. The error was actually in an include not the async code itself. Finding it was one thing. Then trying to figure out why there was an error was a different story.

I had a query output where one of the columns was "client". Now, normally this would not be an issue. However, there was an error in the query so the column "client" was not in the query. Thus CF tried to use the client scope for the output. Since I was trying to output a simple value "#client#" it threw an error "Complex object types cannot be converted to simple values".

The moral of the story:

Avoid using CF objects like "client" as column names.

--Dave