<?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"
	>
<channel>
	<title>Comments on: Doing Relevance Ranked Full-Text Searches In MySQL</title>
	<atom:link href="http://maisonbisson.com/blog/post/10752/making-mysql-do-relevance-ranked-full-text-searches/feed" rel="self" type="application/rss+xml" />
	<link>http://maisonbisson.com/blog/post/10752/making-mysql-do-relevance-ranked-full-text-searches/</link>
	<description>A bunch of stuff I would have emailed you about.</description>
	<pubDate>Sat, 30 Aug 2008 15:29:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Rohan Shenoy</title>
		<link>http://maisonbisson.com/blog/post/10752/making-mysql-do-relevance-ranked-full-text-searches/#comment-191827</link>
		<dc:creator>Rohan Shenoy</dc:creator>
		<pubDate>Tue, 01 Apr 2008 16:11:47 +0000</pubDate>
		<guid isPermaLink="false">http://maisonbisson.com/blog/?p=10752#comment-191827</guid>
		<description>Thanks Maison, was looking for it. I wanted to sort the results of SELECT query by releveance. But I was stuck with '%LIKE%'. You have helped me out.

Thanks a lot dear!</description>
		<content:encoded><![CDATA[<p>Thanks Maison, was looking for it. I wanted to sort the results of SELECT query by releveance. But I was stuck with &#8216;%LIKE%&#8217;. You have helped me out.</p>
<p>Thanks a lot dear!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: taz4mfsd</title>
		<link>http://maisonbisson.com/blog/post/10752/making-mysql-do-relevance-ranked-full-text-searches/#comment-191126</link>
		<dc:creator>taz4mfsd</dc:creator>
		<pubDate>Sat, 08 Mar 2008 23:21:36 +0000</pubDate>
		<guid isPermaLink="false">http://maisonbisson.com/blog/?p=10752#comment-191126</guid>
		<description>sexy gierls</description>
		<content:encoded><![CDATA[<p>sexy gierls</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Epsilon-Delta &#187; Dissecting MySQL Fulltext Indexing</title>
		<link>http://maisonbisson.com/blog/post/10752/making-mysql-do-relevance-ranked-full-text-searches/#comment-37670</link>
		<dc:creator>Epsilon-Delta &#187; Dissecting MySQL Fulltext Indexing</dc:creator>
		<pubDate>Wed, 17 May 2006 17:25:36 +0000</pubDate>
		<guid isPermaLink="false">http://maisonbisson.com/blog/?p=10752#comment-37670</guid>
		<description>[...] MySQL provides two types of fulltext searches - boolean and natural language. Iâ€™m going to focus on the natural language search because it is more mathematically intense. The underlying concept behind the method used in MySQL is that each term in each document is assigned a specific weight which is used to decide a queryâ€™s â€œdistanceâ€ or â€œscoreâ€ with respect to that document. The weights are assigned such that the weight is increased if the term occurs frequently in the document, but decreased in the term occurs frequently among all documents. For a description of how the weights are computed, check out the MySQL documentation. For the curious reader, this article also explains the computation of word-document weights. There are also a slew of articles on using fulltext search in practice. [...]</description>
		<content:encoded><![CDATA[<p>[...] MySQL provides two types of fulltext searches - boolean and natural language. Iâ€™m going to focus on the natural language search because it is more mathematically intense. The underlying concept behind the method used in MySQL is that each term in each document is assigned a specific weight which is used to decide a queryâ€™s â€œdistanceâ€ or â€œscoreâ€ with respect to that document. The weights are assigned such that the weight is increased if the term occurs frequently in the document, but decreased in the term occurs frequently among all documents. For a description of how the weights are computed, check out the MySQL documentation. For the curious reader, this article also explains the computation of word-document weights. There are also a slew of articles on using fulltext search in practice. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mansoor</title>
		<link>http://maisonbisson.com/blog/post/10752/making-mysql-do-relevance-ranked-full-text-searches/#comment-36273</link>
		<dc:creator>mansoor</dc:creator>
		<pubDate>Fri, 28 Apr 2006 21:27:21 +0000</pubDate>
		<guid isPermaLink="false">http://maisonbisson.com/blog/?p=10752#comment-36273</guid>
		<description>salam dostaneh man harkasi keh mikad ba yek pesarehg 29 saleh mogarad va lisanseh mekanik az thran azdevag koneh ageh be tafahoom residim baram emall bezareh</description>
		<content:encoded><![CDATA[<p>salam dostaneh man harkasi keh mikad ba yek pesarehg 29 saleh mogarad va lisanseh mekanik az thran azdevag koneh ageh be tafahoom residim baram emall bezareh</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Is Sun&#8217;s T2000 Up To It? &#171; MaisonBisson.com</title>
		<link>http://maisonbisson.com/blog/post/10752/making-mysql-do-relevance-ranked-full-text-searches/#comment-32253</link>
		<dc:creator>Is Sun&#8217;s T2000 Up To It? &#171; MaisonBisson.com</dc:creator>
		<pubDate>Mon, 27 Feb 2006 01:33:39 +0000</pubDate>
		<guid isPermaLink="false">http://maisonbisson.com/blog/?p=10752#comment-32253</guid>
		<description>[...] And I&#8217;m fully confident that when I put our entire catalog into WPopac, all 330,000 bib records (resulting in about 6.2 million atomic records), performance will still be up to the task. And my math suggests everything should be ducky on a relatively budget server up beyond about 1 million bib records), but what happens for libraries that have more than that, say, perhaps 6 to 8 million bib records (again, 110 to 150 million atomic records; again, all full-text indexed in MySQL)? [...]</description>
		<content:encoded><![CDATA[<p>[...] And I&#8217;m fully confident that when I put our entire catalog into WPopac, all 330,000 bib records (resulting in about 6.2 million atomic records), performance will still be up to the task. And my math suggests everything should be ducky on a relatively budget server up beyond about 1 million bib records), but what happens for libraries that have more than that, say, perhaps 6 to 8 million bib records (again, 110 to 150 million atomic records; again, all full-text indexed in MySQL)? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pulni´s private News &#187; Volltextsuche</title>
		<link>http://maisonbisson.com/blog/post/10752/making-mysql-do-relevance-ranked-full-text-searches/#comment-31809</link>
		<dc:creator>Pulni´s private News &#187; Volltextsuche</dc:creator>
		<pubDate>Tue, 14 Feb 2006 17:33:10 +0000</pubDate>
		<guid isPermaLink="false">http://maisonbisson.com/blog/?p=10752#comment-31809</guid>
		<description>[...] MySQL provides two types of fulltext searches - boolean and natural language. Iâ€™m going to focus on the natural language search because it is more mathematically intense. The underlying concept behind the method used in MySQL is that each term in each document is assigned a specific weight which is used to decide a queryâ€™s â€œdistanceâ€ or â€œscoreâ€ with respect to that document. The weights are assigned such that the weight is increased if the term occurs frequently in the document, but decreased in the term occurs frequently among all documents. For a description of how the weights are computed, check out the MySQL documentation. For the curious reader, this article also explains the computation of word-document weights. There are also a slew of articles on using fulltext search in practice. [...]</description>
		<content:encoded><![CDATA[<p>[...] MySQL provides two types of fulltext searches - boolean and natural language. Iâ€™m going to focus on the natural language search because it is more mathematically intense. The underlying concept behind the method used in MySQL is that each term in each document is assigned a specific weight which is used to decide a queryâ€™s â€œdistanceâ€ or â€œscoreâ€ with respect to that document. The weights are assigned such that the weight is increased if the term occurs frequently in the document, but decreased in the term occurs frequently among all documents. For a description of how the weights are computed, check out the MySQL documentation. For the curious reader, this article also explains the computation of word-document weights. There are also a slew of articles on using fulltext search in practice. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Epsilon-Delta: Mathematics and Computer Programming &#187; Dissecting MySQL Fulltext Indexing</title>
		<link>http://maisonbisson.com/blog/post/10752/making-mysql-do-relevance-ranked-full-text-searches/#comment-31646</link>
		<dc:creator>Epsilon-Delta: Mathematics and Computer Programming &#187; Dissecting MySQL Fulltext Indexing</dc:creator>
		<pubDate>Thu, 09 Feb 2006 01:53:12 +0000</pubDate>
		<guid isPermaLink="false">http://maisonbisson.com/blog/?p=10752#comment-31646</guid>
		<description>[...] MySQL provides two types of fulltext searches - boolean and natural language. I&#8217;m going to focus on the natural language search because it is more mathematically intense. The underlying concept behind the method used in MySQL is that each term in each document is assigned a specific weight which is used to decide a query&#8217;s &#8220;distance&#8221; or &#8220;score&#8221; with respect to that document. The weights are assigned such that the weight is increased if the term occurs frequently in the document, but decreased in the term occurs frequently among all documents. For a description of how the weights are computed, check out the MySQL documentation. For the curious reader, this article also explains the computation of word-document weights. There are also a slew of articles on using fulltext search in practice. [...]</description>
		<content:encoded><![CDATA[<p>[...] MySQL provides two types of fulltext searches - boolean and natural language. I&#8217;m going to focus on the natural language search because it is more mathematically intense. The underlying concept behind the method used in MySQL is that each term in each document is assigned a specific weight which is used to decide a query&#8217;s &#8220;distance&#8221; or &#8220;score&#8221; with respect to that document. The weights are assigned such that the weight is increased if the term occurs frequently in the document, but decreased in the term occurs frequently among all documents. For a description of how the weights are computed, check out the MySQL documentation. For the curious reader, this article also explains the computation of word-document weights. There are also a slew of articles on using fulltext search in practice. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Plesk Bites &#171; MaisonBisson.com</title>
		<link>http://maisonbisson.com/blog/post/10752/making-mysql-do-relevance-ranked-full-text-searches/#comment-30429</link>
		<dc:creator>Plesk Bites &#171; MaisonBisson.com</dc:creator>
		<pubDate>Fri, 27 Jan 2006 00:59:52 +0000</pubDate>
		<guid isPermaLink="false">http://maisonbisson.com/blog/?p=10752#comment-30429</guid>
		<description>[...] Why? Because MySQL 3.x doesn&#8217;t support query caching, boolean full-text searching, or complex subqueries. [...]</description>
		<content:encoded><![CDATA[<p>[...] Why? Because MySQL 3.x doesn&#8217;t support query caching, boolean full-text searching, or complex subqueries. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
