<?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: Paginating large datasets with MySQL</title>
	<atom:link href="http://www.erichynds.com/coldfusion/paginating-large-datasets-with-mysql/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.erichynds.com/coldfusion/paginating-large-datasets-with-mysql/</link>
	<description>Web Developer&#039;s Ramblings on JavaScript, jQuery, ColdFusion, MySQL, and other technologies.</description>
	<lastBuildDate>Wed, 04 Jan 2012 16:01:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Neil Pugh</title>
		<link>http://www.erichynds.com/coldfusion/paginating-large-datasets-with-mysql/#comment-4348</link>
		<dc:creator>Neil Pugh</dc:creator>
		<pubDate>Sun, 19 Dec 2010 13:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.erichynds.com/blog/?p=27#comment-4348</guid>
		<description>You don&#039;t need the cftransaction. The FOUND_ROWS() function works per connection. Each ColdFusion request it seems establishes it&#039;s own connection. I tested this with 2 requests, one made to sleep with the other quickly did it&#039;s work.</description>
		<content:encoded><![CDATA[<p>You don&#8217;t need the cftransaction. The FOUND_ROWS() function works per connection. Each ColdFusion request it seems establishes it&#8217;s own connection. I tested this with 2 requests, one made to sleep with the other quickly did it&#8217;s work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Nadel</title>
		<link>http://www.erichynds.com/coldfusion/paginating-large-datasets-with-mysql/#comment-1414</link>
		<dc:creator>Ben Nadel</dc:creator>
		<pubDate>Tue, 17 Nov 2009 14:35:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.erichynds.com/blog/?p=27#comment-1414</guid>
		<description>Very awesome! I did not know that this existed at all.</description>
		<content:encoded><![CDATA[<p>Very awesome! I did not know that this existed at all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Nadel</title>
		<link>http://www.erichynds.com/coldfusion/paginating-large-datasets-with-mysql/#comment-3853</link>
		<dc:creator>Ben Nadel</dc:creator>
		<pubDate>Tue, 17 Nov 2009 14:35:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.erichynds.com/blog/?p=27#comment-3853</guid>
		<description>Very awesome! I did not know that this existed at all.</description>
		<content:encoded><![CDATA[<p>Very awesome! I did not know that this existed at all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Longnion</title>
		<link>http://www.erichynds.com/coldfusion/paginating-large-datasets-with-mysql/#comment-809</link>
		<dc:creator>Aaron Longnion</dc:creator>
		<pubDate>Thu, 27 Aug 2009 14:34:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.erichynds.com/blog/?p=27#comment-809</guid>
		<description>Great stuff Eric! We need this!</description>
		<content:encoded><![CDATA[<p>Great stuff Eric! We need this!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Longnion</title>
		<link>http://www.erichynds.com/coldfusion/paginating-large-datasets-with-mysql/#comment-3852</link>
		<dc:creator>Aaron Longnion</dc:creator>
		<pubDate>Thu, 27 Aug 2009 14:34:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.erichynds.com/blog/?p=27#comment-3852</guid>
		<description>Great stuff Eric! We need this!</description>
		<content:encoded><![CDATA[<p>Great stuff Eric! We need this!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Hynds</title>
		<link>http://www.erichynds.com/coldfusion/paginating-large-datasets-with-mysql/#comment-808</link>
		<dc:creator>Eric Hynds</dc:creator>
		<pubDate>Thu, 27 Aug 2009 02:02:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.erichynds.com/blog/?p=27#comment-808</guid>
		<description>Good catch... I typed this post up a little too quick earlier.   It&#039;s a normal select statement except you place the SQL_CALC_FOUND_ROWS option right after the &quot;SELECT&quot; keyword, before the list of fields you&#039;re selecting.</description>
		<content:encoded><![CDATA[<p>Good catch&#8230; I typed this post up a little too quick earlier.   It&#8217;s a normal select statement except you place the SQL_CALC_FOUND_ROWS option right after the &#8220;SELECT&#8221; keyword, before the list of fields you&#8217;re selecting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.erichynds.com/coldfusion/paginating-large-datasets-with-mysql/#comment-3851</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 27 Aug 2009 02:02:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.erichynds.com/blog/?p=27#comment-3851</guid>
		<description>Good catch... I typed this post up a little too quick earlier.   It&#039;s a normal select statement except you place the SQL_CALC_FOUND_ROWS option right after the &quot;SELECT&quot; keyword, before the list of fields you&#039;re selecting.</description>
		<content:encoded><![CDATA[<p>Good catch&#8230; I typed this post up a little too quick earlier.   It&#8217;s a normal select statement except you place the SQL_CALC_FOUND_ROWS option right after the &#8220;SELECT&#8221; keyword, before the list of fields you&#8217;re selecting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve 'Cutter' Blades</title>
		<link>http://www.erichynds.com/coldfusion/paginating-large-datasets-with-mysql/#comment-807</link>
		<dc:creator>Steve 'Cutter' Blades</dc:creator>
		<pubDate>Thu, 27 Aug 2009 01:44:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.erichynds.com/blog/?p=27#comment-807</guid>
		<description>This is interesting stuff, but can you show a more complete SQL example? In your current example, you only show SQL_CALC_FOUND_ROWS in the SELECT clause. How would this work if you only wanted 2 or 3 columns of data, from 2 or more tables connected via a foreign key?</description>
		<content:encoded><![CDATA[<p>This is interesting stuff, but can you show a more complete SQL example? In your current example, you only show SQL_CALC_FOUND_ROWS in the SELECT clause. How would this work if you only wanted 2 or 3 columns of data, from 2 or more tables connected via a foreign key?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve 'Cutter' Blades</title>
		<link>http://www.erichynds.com/coldfusion/paginating-large-datasets-with-mysql/#comment-3850</link>
		<dc:creator>Steve 'Cutter' Blades</dc:creator>
		<pubDate>Thu, 27 Aug 2009 01:44:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.erichynds.com/blog/?p=27#comment-3850</guid>
		<description>This is interesting stuff, but can you show a more complete SQL example? In your current example, you only show SQL_CALC_FOUND_ROWS in the SELECT clause. How would this work if you only wanted 2 or 3 columns of data, from 2 or more tables connected via a foreign key?</description>
		<content:encoded><![CDATA[<p>This is interesting stuff, but can you show a more complete SQL example? In your current example, you only show SQL_CALC_FOUND_ROWS in the SELECT clause. How would this work if you only wanted 2 or 3 columns of data, from 2 or more tables connected via a foreign key?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

