<?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: The Bomb vs The Rifle: Effective data searching</title>
	<atom:link href="http://www.heavyworks.net/blog/posts/the-bomb-vs-the-rifle-effective-data-searching/feed" rel="self" type="application/rss+xml" />
	<link>http://www.heavyworks.net/blog/posts/the-bomb-vs-the-rifle-effective-data-searching</link>
	<description>Extreme Software Engineering</description>
	<lastBuildDate>Wed, 08 Sep 2010 06:45:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Bruno Lustosa</title>
		<link>http://www.heavyworks.net/blog/posts/the-bomb-vs-the-rifle-effective-data-searching/comment-page-1#comment-24</link>
		<dc:creator>Bruno Lustosa</dc:creator>
		<pubDate>Mon, 29 Dec 2008 21:03:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.heavyworks.net/?p=115#comment-24</guid>
		<description>That&#039;s it, searching with LIKE is very very bad when your database has searched beyond a few hundred rows.
When you have multiple fields (or tables)to search, things become much worse, because you have to combine several LIKE searchs with an OR, which will not run fast, even with text indexing on the fields.</description>
		<content:encoded><![CDATA[<p>That&#8217;s it, searching with LIKE is very very bad when your database has searched beyond a few hundred rows.<br />
When you have multiple fields (or tables)to search, things become much worse, because you have to combine several LIKE searchs with an OR, which will not run fast, even with text indexing on the fields.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
