<?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: You can&#8217;t sort and scale</title>
	<atom:link href="http://agilewebmasters.com/robert/you-cant-sort-and-scale/feed/" rel="self" type="application/rss+xml" />
	<link>http://agilewebmasters.com/robert/you-cant-sort-and-scale/</link>
	<description>Take the lead out...</description>
	<lastBuildDate>Fri, 25 Nov 2011 17:58:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: robert</title>
		<link>http://agilewebmasters.com/robert/you-cant-sort-and-scale/#comment-8</link>
		<dc:creator>robert</dc:creator>
		<pubDate>Sun, 03 Aug 2008 05:32:55 +0000</pubDate>
		<guid isPermaLink="false">http://agilewebmasters.com/?p=25#comment-8</guid>
		<description>Thanks for making that initial jumble clearer. I&#039;ll do a follow up sometime on specific use cases and how to work around the long/impossible queries.</description>
		<content:encoded><![CDATA[<p>Thanks for making that initial jumble clearer. I&#8217;ll do a follow up sometime on specific use cases and how to work around the long/impossible queries.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Ashley</title>
		<link>http://agilewebmasters.com/robert/you-cant-sort-and-scale/#comment-5</link>
		<dc:creator>Nick Ashley</dc:creator>
		<pubDate>Sat, 02 Aug 2008 16:48:30 +0000</pubDate>
		<guid isPermaLink="false">http://agilewebmasters.com/?p=25#comment-5</guid>
		<description>Great post. I just wanted to clarify one thing. When limiting your resultset using the WHERE, it will return the correct items you need for the given page. However, these results themselves aren&#039;t necessary in the correct order for the page. (You will get positions 50-60, but not in numerical order). So you still need to ORDER BY to get what your looking for. The point Robert is making, is that by using a WHERE clause first, you are only ordering 10 posts, as opposed to all previous posts.</description>
		<content:encoded><![CDATA[<p>Great post. I just wanted to clarify one thing. When limiting your resultset using the WHERE, it will return the correct items you need for the given page. However, these results themselves aren&#8217;t necessary in the correct order for the page. (You will get positions 50-60, but not in numerical order). So you still need to ORDER BY to get what your looking for. The point Robert is making, is that by using a WHERE clause first, you are only ordering 10 posts, as opposed to all previous posts.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

