<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0">


<channel>
<title>SQLPlex | Database technology community - 5 Recently Added Articles</title>
<link>http://www.sqlplex.com</link>
<description>This RSS Feed contains 5 recently added articles to the knowledge base. You can click on the title to view its content.   Knowledge Base (http://www.sqlplex.com)</description>
<item>

                                        <guid>http://www.sqlplex.com/article-384.html</guid>

                                        <title>Multiple column index vs multiple indexes</title>

                                        <link>http://www.sqlplex.com/article-384.html</link>

                                        <description><![CDATA[
<p>After my <a href="http://www.mysqlperformanceblog.com/2008/08/21/how-to-find-wrong-indexing-with-glance-view/" ca_clicked="0">previous post</a>
there were questions raised about Index Merge on Multiple Inde]]></description>

                                </item>
<item>

                                        <guid>http://www.sqlplex.com/article-383.html</guid>

                                        <title>101 Reasons Why PostgreSQL is a better fit for Rails than MySQL</title>

                                        <link>http://www.sqlplex.com/article-383.html</link>

                                        <description><![CDATA[1 - Indexing Support<br />
<br />
MySQL cannot utilize more than one index
per query. I believe this is worth repeating: MySQL CANNOT UTILIZE MORE
THAN ONE INDEX PER QUERY. Wait till your tables get large enough and
this will surely ]]></description>

                                </item>
<item>

                                        <guid>http://www.sqlplex.com/article-382.html</guid>

                                        <title>New partitioning features</title>

                                        <link>http://www.sqlplex.com/article-382.html</link>

                                        <description><![CDATA[As burtonator pointed out parallelism is an important<br />
feature that partitioning makes possible. So I thought<br />
it might be a good idea to mention a little bit what<br />
we&#39re doing in the area of partitioning.<br]]></description>

                                </item>
<item>

                                        <guid>http://www.sqlplex.com/article-381.html</guid>

                                        <title>Oracle Magazine - September/October</title>

                                        <link>http://www.sqlplex.com/article-381.html</link>

                                        <description><![CDATA[
<meta content="text/html; charset=utf-8" http-equiv="Content-Type"></meta>
<meta content="Word.Document" name="ProgId"></meta>
<meta content="Microsoft Word 12" name=&qu]]></description>

                                </item>
<item>

                                        <guid>http://www.sqlplex.com/article-371.html</guid>

                                        <title>Union vs Union All</title>

                                        <link>http://www.sqlplex.com/article-371.html</link>

                                        <description><![CDATA[

<p> In short, UNION does a sort-unique on both collections. UNION ALL just 
retrieves all rows, regardless of any double values.</p>










<p>I came across a (similar) piece of code during my work at BT:</p&gt]]></description>

                                </item>

</channel>

</rss>