Not
sure that's the point, Todd. What if he's using a database that doesn't
support stored procedures? I think the point is that in some cases,
cfinclude behaves in different ways, and aside from trial-and-error there's
really no way to know for sure how it's going to respond.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Todd Rafferty
Sent: Friday, January 30, 2004 4:10 PM
To: [EMAIL PROTECTED]
Subject: Re: [CFCDev] More CFMX Excellence with Component Inheritance
I call that bad coding? No reason for cfincludes to be that way, if your sql statement is that large with conditionals and such, it should be a storedproc.
~Todd
Adam Cameron wrote:
I think that cfinclude is not cut + paste, and it IS the expectedbehavior that you cannot have CFC-specific tags within an included template. cfargument and cfreturn are integral parts of the cffunction tag, I can show you a file I <cfinclude> that is chock full of <cfqueryparam> tags, and not a <cfquery> tag in sight. So how does that work, then? Adam
