<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Functional difference between &#8220;NOT IN&#8221; vs &#8220;NOT EXISTS&#8221; clauses</title>
	<atom:link href="http://decipherinfosys.wordpress.com/2007/01/21/32/feed/" rel="self" type="application/rss+xml" />
	<link>http://decipherinfosys.wordpress.com/2007/01/21/32/</link>
	<description></description>
	<lastBuildDate>Mon, 14 Dec 2009 05:18:20 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: IN vs. EXISTS vs. JOIN : Sean Holtshousen &#8211; Developer Blog</title>
		<link>http://decipherinfosys.wordpress.com/2007/01/21/32/#comment-5425</link>
		<dc:creator>IN vs. EXISTS vs. JOIN : Sean Holtshousen &#8211; Developer Blog</dc:creator>
		<pubDate>Wed, 04 Nov 2009 13:09:05 +0000</pubDate>
		<guid isPermaLink="false">http://decipherinfosys.wordpress.com/2007/01/21/32/#comment-5425</guid>
		<description>[...] in one scenario – read this post for the differences between NOT IN and NOT EXISTS clauses : http://decipherinfosys.wordpress.com/2007/01/21/32/ ). However, there are performance implications of using one over the other that one needs to be [...]</description>
		<content:encoded><![CDATA[<p>[...] in one scenario – read this post for the differences between NOT IN and NOT EXISTS clauses : <a href="http://decipherinfosys.wordpress.com/2007/01/21/32/" rel="nofollow">http://decipherinfosys.wordpress.com/2007/01/21/32/</a> ). However, there are performance implications of using one over the other that one needs to be [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: workarounds for mysql NOT IN and NOT EXISTS information &#171; Coral&#39;s Blog</title>
		<link>http://decipherinfosys.wordpress.com/2007/01/21/32/#comment-4990</link>
		<dc:creator>workarounds for mysql NOT IN and NOT EXISTS information &#171; Coral&#39;s Blog</dc:creator>
		<pubDate>Thu, 18 Jun 2009 13:23:41 +0000</pubDate>
		<guid isPermaLink="false">http://decipherinfosys.wordpress.com/2007/01/21/32/#comment-4990</guid>
		<description>[...] It also seems that NOT IN is inclined to do full table scans on the subquery where as NOT EXISTS can use an index which means that but NOT EXISTS has better performance.. More information on the difference here. [...]</description>
		<content:encoded><![CDATA[<p>[...] It also seems that NOT IN is inclined to do full table scans on the subquery where as NOT EXISTS can use an index which means that but NOT EXISTS has better performance.. More information on the difference here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IN vs EXISTS &#171; Systems Engineering and RDBMS</title>
		<link>http://decipherinfosys.wordpress.com/2007/01/21/32/#comment-3</link>
		<dc:creator>IN vs EXISTS &#171; Systems Engineering and RDBMS</dc:creator>
		<pubDate>Tue, 30 Jan 2007 16:56:02 +0000</pubDate>
		<guid isPermaLink="false">http://decipherinfosys.wordpress.com/2007/01/21/32/#comment-3</guid>
		<description>[...] in one scenario - read this post for the differences between NOT IN and NOT EXISTS clauses : http://decipherinfosys.wordpress.com/2007/01/21/32/ ). However, there are performance implications of using one over the other that one needs to be [...]</description>
		<content:encoded><![CDATA[<p>[...] in one scenario &#8211; read this post for the differences between NOT IN and NOT EXISTS clauses : <a href="http://decipherinfosys.wordpress.com/2007/01/21/32/" rel="nofollow">http://decipherinfosys.wordpress.com/2007/01/21/32/</a> ). However, there are performance implications of using one over the other that one needs to be [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
