<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: CF8 Bug Fixed</title>
	<atom:link href="http://www.barneyb.com/barneyblog/2007/06/13/cf8-bug-fixed/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.barneyb.com/barneyblog/2007/06/13/cf8-bug-fixed/</link>
	<description>Thoughts, rants, and even some code from the mind of Barney Boisvert.</description>
	<lastBuildDate>Thu, 11 Sep 2014 09:58:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: barneyb</title>
		<link>https://www.barneyb.com/barneyblog/2007/06/13/cf8-bug-fixed/comment-page-1/#comment-20683</link>
		<dc:creator>barneyb</dc:creator>
		<pubDate>Thu, 14 Jun 2007 15:44:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.barneyb.com/barneyblog/2007/06/13/cf8-bug-fixed/#comment-20683</guid>
		<description>&lt;p&gt;The main source of empty CFQUERY NAME attributes is generated code.  I use a snippet in CFEclipse for creating ad hoc CFQUERY tags, and it has a dialog with a &#039;name&#039; field.  For queries that don&#039;t return a result set, I just leave it blank.&lt;/p&gt;
&lt;p&gt;I also generate a fair amount of CFML (mostly data access CFCs), and I have routines that assemble my queries, and they do much the same thing: if no name for the query is required, it just leaves it as the empty string, rather than adding logic to remove the empty NAME attribute.&lt;/p&gt;
&lt;p&gt;With large-scale generation, I do more static generation than dynamic generation, which means all the code I&#039;ve already generated is developer-edited, not regenerated.  The dynamic stuff is easy, just update the generator and regenerate.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>The main source of empty CFQUERY NAME attributes is generated code.  I use a snippet in CFEclipse for creating ad hoc CFQUERY tags, and it has a dialog with a 'name' field.  For queries that don't return a result set, I just leave it blank.</p>
<p>I also generate a fair amount of CFML (mostly data access CFCs), and I have routines that assemble my queries, and they do much the same thing: if no name for the query is required, it just leaves it as the empty string, rather than adding logic to remove the empty NAME attribute.</p>
<p>With large-scale generation, I do more static generation than dynamic generation, which means all the code I've already generated is developer-edited, not regenerated.  The dynamic stuff is easy, just update the generator and regenerate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Nadel</title>
		<link>https://www.barneyb.com/barneyblog/2007/06/13/cf8-bug-fixed/comment-page-1/#comment-20658</link>
		<dc:creator>Ben Nadel</dc:creator>
		<pubDate>Thu, 14 Jun 2007 11:27:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.barneyb.com/barneyblog/2007/06/13/cf8-bug-fixed/#comment-20658</guid>
		<description>I never hear back from bug submissions (pout pout pout) :)

This is a strange &quot;bug&quot;. I had never even though of leaving the name attribute blank. I only came across that for the first time a few months ago. I like to use the query name attribute because I feel that it gives one more piece of documentation as to what is going on:

....

I know this query is deleting join relationships to whatever main item I am viewing, and the name allows me to do this without even looking at the query content.

Just a personal preference. 

Regardless, that is awesome that Adobe got right on top of it. Just another reason they rock :D</description>
		<content:encoded><![CDATA[<p>I never hear back from bug submissions (pout pout pout) :)</p>
<p>This is a strange "bug". I had never even though of leaving the name attribute blank. I only came across that for the first time a few months ago. I like to use the query name attribute because I feel that it gives one more piece of documentation as to what is going on:</p>
<p>&#8230;.</p>
<p>I know this query is deleting join relationships to whatever main item I am viewing, and the name allows me to do this without even looking at the query content.</p>
<p>Just a personal preference. </p>
<p>Regardless, that is awesome that Adobe got right on top of it. Just another reason they rock :D</p>
]]></content:encoded>
	</item>
</channel>
</rss>
