<?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: Do you always need index on WHERE column ?</title>
	<atom:link href="http://www.mysqlperformanceblog.com/2007/08/28/do-you-always-need-index-on-where-column/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mysqlperformanceblog.com/2007/08/28/do-you-always-need-index-on-where-column/</link>
	<description>Everything about MySQL Performance</description>
	<lastBuildDate>Sat, 21 Nov 2009 05:23:57 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: RNT</title>
		<link>http://www.mysqlperformanceblog.com/2007/08/28/do-you-always-need-index-on-where-column/comment-page-1/#comment-399525</link>
		<dc:creator>RNT</dc:creator>
		<pubDate>Tue, 02 Dec 2008 11:42:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/08/28/do-you-always-need-index-on-where-column/#comment-399525</guid>
		<description>Thanks for sharing.

&lt;a href=&quot;http://www.rntsolutions.com/&quot; rel=&quot;nofollow&quot;&gt;R&amp;T SOlutions&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Thanks for sharing.</p>
<p><a href="http://www.rntsolutions.com/" rel="nofollow">R&amp;T SOlutions</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sergio</title>
		<link>http://www.mysqlperformanceblog.com/2007/08/28/do-you-always-need-index-on-where-column/comment-page-1/#comment-333033</link>
		<dc:creator>Sergio</dc:creator>
		<pubDate>Wed, 23 Jul 2008 00:04:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/08/28/do-you-always-need-index-on-where-column/#comment-333033</guid>
		<description>That&#039;s why my queries took some time (with &amp; without index)..
 
I have a tinint column that takes only 1 and 0 values. 
There are about 164000+ rows. Almost all have 0 value, just some of the rows have 1 (in general &lt; 10).

To be more specific, the column name is &quot;file_hidden&quot;. If the value is 1, then that row is not shown to public..

SELECT * FROM files WHERE file_hidden = 0

I guess the only solution in this situation is to use two tables with the same structure.. one for &quot;1&quot; (hidden from public), one for &quot;0&quot; (visible to public) rows</description>
		<content:encoded><![CDATA[<p>That&#8217;s why my queries took some time (with &amp; without index)..</p>
<p>I have a tinint column that takes only 1 and 0 values.<br />
There are about 164000+ rows. Almost all have 0 value, just some of the rows have 1 (in general &lt; 10).</p>
<p>To be more specific, the column name is &#8220;file_hidden&#8221;. If the value is 1, then that row is not shown to public..</p>
<p>SELECT * FROM files WHERE file_hidden = 0</p>
<p>I guess the only solution in this situation is to use two tables with the same structure.. one for &#8220;1&#8243; (hidden from public), one for &#8220;0&#8243; (visible to public) rows</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Son Nguyen</title>
		<link>http://www.mysqlperformanceblog.com/2007/08/28/do-you-always-need-index-on-where-column/comment-page-1/#comment-322354</link>
		<dc:creator>Son Nguyen</dc:creator>
		<pubDate>Thu, 03 Jul 2008 23:02:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/08/28/do-you-always-need-index-on-where-column/#comment-322354</guid>
		<description>What are the possible alternatives to this particular example? When skipping index is faster but not the best? Creating a summary table? Or something else? I&#039;d like to learn from the experts.</description>
		<content:encoded><![CDATA[<p>What are the possible alternatives to this particular example? When skipping index is faster but not the best? Creating a summary table? Or something else? I&#8217;d like to learn from the experts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johhny</title>
		<link>http://www.mysqlperformanceblog.com/2007/08/28/do-you-always-need-index-on-where-column/comment-page-1/#comment-304161</link>
		<dc:creator>Johhny</dc:creator>
		<pubDate>Fri, 23 May 2008 08:59:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/08/28/do-you-always-need-index-on-where-column/#comment-304161</guid>
		<description>Very interesting website. Keep up the outstanding work and thank you...</description>
		<content:encoded><![CDATA[<p>Very interesting website. Keep up the outstanding work and thank you&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Making ActiveRecord faster by NOT indexing - Blog - ShiftEleven</title>
		<link>http://www.mysqlperformanceblog.com/2007/08/28/do-you-always-need-index-on-where-column/comment-page-1/#comment-289864</link>
		<dc:creator>Making ActiveRecord faster by NOT indexing - Blog - ShiftEleven</dc:creator>
		<pubDate>Tue, 29 Apr 2008 17:00:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/08/28/do-you-always-need-index-on-where-column/#comment-289864</guid>
		<description>[...] Usually one of the first things I read about on how to speed up ActiveRecord is to index my columns to speed up the lookup of items. &#8220;Of course!&#8221; But could indexing too much be harmful? [...]</description>
		<content:encoded><![CDATA[<p>[...] Usually one of the first things I read about on how to speed up ActiveRecord is to index my columns to speed up the lookup of items. &#8220;Of course!&#8221; But could indexing too much be harmful? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brahmantyo &#187; Blog Archive &#187; Sifat atau budaya?</title>
		<link>http://www.mysqlperformanceblog.com/2007/08/28/do-you-always-need-index-on-where-column/comment-page-1/#comment-182306</link>
		<dc:creator>Brahmantyo &#187; Blog Archive &#187; Sifat atau budaya?</dc:creator>
		<pubDate>Mon, 29 Oct 2007 13:37:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/08/28/do-you-always-need-index-on-where-column/#comment-182306</guid>
		<description>[...] 2. Vadim Xaprb,What about checking selectivity of indexes ?  http://www.mysqlperformanceblog.com/2007/08/28/do-you-always-need-index-on-where-column/ [...]</description>
		<content:encoded><![CDATA[<p>[...] 2. Vadim Xaprb,What about checking selectivity of indexes ?  <a href="http://www.mysqlperformanceblog.com/2007/08/28/do-you-always-need-index-on-where-column/" rel="nofollow">http://www.mysqlperformanceblog.com/2007/08/28/do-you-always-need-index-on-where-column/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Log Buffer #60: a Carnival of the Vanities for DBAs &#183; Steve Karam &#183; The Oracle Alchemist</title>
		<link>http://www.mysqlperformanceblog.com/2007/08/28/do-you-always-need-index-on-where-column/comment-page-1/#comment-161366</link>
		<dc:creator>Log Buffer #60: a Carnival of the Vanities for DBAs &#183; Steve Karam &#183; The Oracle Alchemist</dc:creator>
		<pubDate>Fri, 31 Aug 2007 16:03:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/08/28/do-you-always-need-index-on-where-column/#comment-161366</guid>
		<description>[...] is all about adding indexes on your WHERE clause columns. Think again! The MySQL Performance Blog posts about cases where an index might not be such a hot idea. This applies to Oracle as well of course, where sometimes a b-tree index just won&#8217;t cut [...]</description>
		<content:encoded><![CDATA[<p>[...] is all about adding indexes on your WHERE clause columns. Think again! The MySQL Performance Blog posts about cases where an index might not be such a hot idea. This applies to Oracle as well of course, where sometimes a b-tree index just won&#8217;t cut [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MySQL Resources &#171; Technikhil Writing</title>
		<link>http://www.mysqlperformanceblog.com/2007/08/28/do-you-always-need-index-on-where-column/comment-page-1/#comment-160609</link>
		<dc:creator>MySQL Resources &#171; Technikhil Writing</dc:creator>
		<pubDate>Thu, 30 Aug 2007 01:10:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/08/28/do-you-always-need-index-on-where-column/#comment-160609</guid>
		<description>[...] is another blog written by MySQL consultants based in Europe. This blog is focussed more on the performance tuning tips for MySQL. Great resource to learn the various settings and variables in MySQL that can be used to [...]</description>
		<content:encoded><![CDATA[<p>[...] is another blog written by MySQL consultants based in Europe. This blog is focussed more on the performance tuning tips for MySQL. Great resource to learn the various settings and variables in MySQL that can be used to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://www.mysqlperformanceblog.com/2007/08/28/do-you-always-need-index-on-where-column/comment-page-1/#comment-160418</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Wed, 29 Aug 2007 13:46:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/08/28/do-you-always-need-index-on-where-column/#comment-160418</guid>
		<description>Thanks Mark,

Even thought this is post by Vadim not me :)

The other important thing to remember about selectivity - it is actually selectivity of value what matters.  It is well possible to have column with 2 values indexes if one of them is in 99% of values and other is in 1% and have index well used to retrieve the data for that 1%

Too bad MySQL does not have partial indexes though (I mean so only that 1% could really be indexed)</description>
		<content:encoded><![CDATA[<p>Thanks Mark,</p>
<p>Even thought this is post by Vadim not me <img src='http://www.mysqlperformanceblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>The other important thing to remember about selectivity &#8211; it is actually selectivity of value what matters.  It is well possible to have column with 2 values indexes if one of them is in 99% of values and other is in 1% and have index well used to retrieve the data for that 1%</p>
<p>Too bad MySQL does not have partial indexes though (I mean so only that 1% could really be indexed)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arnold Daniels</title>
		<link>http://www.mysqlperformanceblog.com/2007/08/28/do-you-always-need-index-on-where-column/comment-page-1/#comment-160395</link>
		<dc:creator>Arnold Daniels</dc:creator>
		<pubDate>Wed, 29 Aug 2007 12:53:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/08/28/do-you-always-need-index-on-where-column/#comment-160395</guid>
		<description>There is a sniplet on MySQL forge to find these useless/harmfull indexes. http://forge.mysql.com/snippets/view.php?id=85</description>
		<content:encoded><![CDATA[<p>There is a sniplet on MySQL forge to find these useless/harmfull indexes. <a href="http://forge.mysql.com/snippets/view.php?id=85" rel="nofollow">http://forge.mysql.com/snippets/view.php?id=85</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
