<?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: Faster REGEXP Search</title>
	<atom:link href="http://www.introsites.co.uk/tips/fast-regexp-search-solution.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.introsites.co.uk</link>
	<description>Develop Promote Support</description>
	<lastBuildDate>Mon, 18 Jul 2011 13:10:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Paul Bennett</title>
		<link>http://www.introsites.co.uk/tips/fast-regexp-search-solution.html#comment-235</link>
		<dc:creator>Paul Bennett</dc:creator>
		<pubDate>Tue, 24 Nov 2009 21:25:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.introsites.co.uk#comment-235</guid>
		<description>Hi there,

It looks like the initial LIKE is doing the bulk of the filtering - could this be where the performance gains are coming from?

From what I know, MySQL will optimize the query before running it and will get the first result set using the LIKE and then use the 2nd and 3rd REGEXP&#039;s to filter the result set further before returning it (but I could be wrong)

Paul</description>
		<content:encoded><![CDATA[<p>Hi there,</p>
<p>It looks like the initial LIKE is doing the bulk of the filtering &#8211; could this be where the performance gains are coming from?</p>
<p>From what I know, MySQL will optimize the query before running it and will get the first result set using the LIKE and then use the 2nd and 3rd REGEXP&#8217;s to filter the result set further before returning it (but I could be wrong)</p>
<p>Paul</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mykel</title>
		<link>http://www.introsites.co.uk/tips/fast-regexp-search-solution.html#comment-234</link>
		<dc:creator>mykel</dc:creator>
		<pubDate>Wed, 29 Jul 2009 05:04:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.introsites.co.uk#comment-234</guid>
		<description>Hi,

Looks good, although I think in your specific example the

AND field NOT LIKE &#039;%material%&#039;

portion will exclude some results that you wouldn&#039;t necessarily want to exclude.  e.g. if field was &quot;build materialx&quot; it would be excluded in your optimized but not in the original regex version.</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Looks good, although I think in your specific example the</p>
<p>AND field NOT LIKE &#8216;%material%&#8217;</p>
<p>portion will exclude some results that you wouldn&#8217;t necessarily want to exclude.  e.g. if field was &#8220;build materialx&#8221; it would be excluded in your optimized but not in the original regex version.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nurziya</title>
		<link>http://www.introsites.co.uk/tips/fast-regexp-search-solution.html#comment-233</link>
		<dc:creator>Nurziya</dc:creator>
		<pubDate>Thu, 21 May 2009 10:27:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.introsites.co.uk#comment-233</guid>
		<description>how it works?! some kind of magic?))</description>
		<content:encoded><![CDATA[<p>how it works?! some kind of magic?))</p>
]]></content:encoded>
	</item>
</channel>
</rss>

