<?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: How great is named_scope?</title>
	<atom:link href="http://davedupre.com/2008/12/12/how-great-is-named_scope/feed/" rel="self" type="application/rss+xml" />
	<link>http://davedupre.com/2008/12/12/how-great-is-named_scope/</link>
	<description>Some random thoughts - Go big or stay home!</description>
	<lastBuildDate>Mon, 23 Jan 2012 18:56:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Brian</title>
		<link>http://davedupre.com/2008/12/12/how-great-is-named_scope/comment-page-1/#comment-330</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Sun, 11 Jan 2009 19:14:21 +0000</pubDate>
		<guid isPermaLink="false">http://davedupre.com/?p=137#comment-330</guid>
		<description>That&#039;s a good rule of thumb: if you&#039;re tempted to add :conditions in your code, use a named_scope instead.</description>
		<content:encoded><![CDATA[<p>That&#8217;s a good rule of thumb: if you&#8217;re tempted to add :conditions in your code, use a named_scope instead.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://davedupre.com/2008/12/12/how-great-is-named_scope/comment-page-1/#comment-329</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Sun, 11 Jan 2009 15:19:03 +0000</pubDate>
		<guid isPermaLink="false">http://davedupre.com/?p=137#comment-329</guid>
		<description>Hi there, Brian! I can&#039;t say that I have a definitive strategy, but I do find myself making named scopes for model attributes or sets of attributes that collect records. As much as possible, I want to avoid having anything use a :conditions on my model.  I prefer to keep the details of the model inside the model.</description>
		<content:encoded><![CDATA[<p>Hi there, Brian! I can&#8217;t say that I have a definitive strategy, but I do find myself making named scopes for model attributes or sets of attributes that collect records. As much as possible, I want to avoid having anything use a :conditions on my model.  I prefer to keep the details of the model inside the model.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://davedupre.com/2008/12/12/how-great-is-named_scope/comment-page-1/#comment-327</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Sun, 11 Jan 2009 04:46:18 +0000</pubDate>
		<guid isPermaLink="false">http://davedupre.com/?p=137#comment-327</guid>
		<description>Dave, I found this entry catching up on my reading after the holidays.

I&#039;m also a huge fan of named_scope, and has_finder before it.  But one problem I have had with it is the tendency to make up new named scopes ad hoc.  I worry that they&#039;re inconsistent and obscure.

Do you have any wisdom on a strategy for when and where to create named scopes?</description>
		<content:encoded><![CDATA[<p>Dave, I found this entry catching up on my reading after the holidays.</p>
<p>I&#8217;m also a huge fan of named_scope, and has_finder before it.  But one problem I have had with it is the tendency to make up new named scopes ad hoc.  I worry that they&#8217;re inconsistent and obscure.</p>
<p>Do you have any wisdom on a strategy for when and where to create named scopes?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

