Well, sure, like the point about Select * being bad when you select more than just the columns you need, so too is the benefit of CFQUERYPARAM (from its performance perspective) only valuable for databases that support bind variables (or what SQL Server calls parameterized queries). I'm sorry that I didn't state both points, if anyone felt I should have. I just kind of saw them as a given, but it's totally fair to say that we never know who's reading the list, so we should be as clear as possible.
Indeed, along the same lines, I'll say that it was useful to hear about that observation of a newline within a query being an issue. Do you have that reference still? It might be useful to track down if that could have been a problem in either the DB driver or CF itself, which may since then have been resolved in an update or hotfix. That's a frequent challenge with info we find out there. Even on the Adobe site itself, some info may simply no longer apply--or it could depend on what release/hotfix you have. So it goes back to the point above: we *would* be wise to always challenge even "old saws" and "conventional wisdom". The real answer is to test for ourselves, on our platforms. Of course, doing that well isn't all that easy, which is why we end up with the commonly held theories (and occasional old wives tales). That's what's great about this business. It's a constant challenge to learn and grow. /Charlie http://www.carehart.org/blog/ -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Scott Sent: Thursday, March 01, 2007 10:42 PM To: [email protected] Subject: [cfaussie] Re: @#$!! queryparam Charlie, I did a bit of research into cfqueryparam to see what you meant by ther performance but it is only for those DBMSs that support bind variables anyway. But I also was reading the comments to this and came across a know unwanted feature, I say that because it is not considered a bug by Adobe, or Macromedia / Allaire at that time. It appears that this error can occur when doing something like this. Select * >From Table And not if you have this. Select * From Table But it can, just not as frequent and the solution was to restart the CF Application server until it happened again. But they also said to avoid at all costs using select * from table and to use this Select column1, column2 >From table As the change is more likely to be picked up by the caching of the query. Or you could use the setting in the Administrator for Cached queries and set that to zero. Duncan, I hope that helps you out here. Andrew Scott --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
