RE: [CFCDev] More CFMX Excellence with Component Inheritance

[Jim Davis]

Well that’s kind of harsh considering how little information is known.   Perhaps there are good reasons why it can’t be a stored proc, perhaps the complexity isn’t in conditional logic but rather in parameter acquisition which can’t be done from the data layer, perhaps there is no access to procs in this environment.   I just don’t think that any value judgments can be made here: the bottom line is the behavior of CFINCLUDE is flakey at best.   Jim Davis   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 expected      behavior 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