<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: MySQL is good, except for.... in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/mysql-is-good-except-for/m-p/2883751#M3401</link>
    <description>MySQL is quite nice for lots of general stuff indeed. As for subselects, MySQL doesn't support this. Yet. It's planned and it's already implemented in development version 4.1.&lt;BR /&gt;&lt;BR /&gt;Most of the time, however, you can circumvent a subselect by formulating your query in a different way. Hints about this are on the MySQL-site and probably on lots of other places too.&lt;BR /&gt;&lt;BR /&gt;If you really need subselects (and other SQL-stuff like transactions and views), you could take a look at PostgreSQL (&lt;A href="http://www.postgresql.org)." target="_blank"&gt;http://www.postgresql.org).&lt;/A&gt; PostgreSQL is a lot bigger than MySQL however, and for a reason ;)&lt;BR /&gt;&lt;BR /&gt;Kind regards,&lt;BR /&gt;&lt;BR /&gt;Hans</description>
    <pubDate>Wed, 05 Mar 2003 12:40:30 GMT</pubDate>
    <dc:creator>Hans van Zijst</dc:creator>
    <dc:date>2003-03-05T12:40:30Z</dc:date>
    <item>
      <title>MySQL is good, except for....</title>
      <link>https://community.hpe.com/t5/operating-system-linux/mysql-is-good-except-for/m-p/2883747#M3397</link>
      <description>MySQL is a good database for a lot of general purpose stuff. I have it back-ending my monitoring solution (Nagios) and my intranet server (PHP-Nuke). My only complaint is that it does not do subqueries [i.e. SELECT * FROM orders WHERE (SELECT snum WHERE cnum = 1001)]. That killed most of an afternoon for me until I doublechecked the manuals. :&amp;gt;)</description>
      <pubDate>Thu, 16 Jan 2003 16:35:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/mysql-is-good-except-for/m-p/2883747#M3397</guid>
      <dc:creator>dan dobbs</dc:creator>
      <dc:date>2003-01-16T16:35:00Z</dc:date>
    </item>
    <item>
      <title>Re: MySQL is good, except for....</title>
      <link>https://community.hpe.com/t5/operating-system-linux/mysql-is-good-except-for/m-p/2883748#M3398</link>
      <description>Which is funny, because that is the #1 reason people usually have for not using MySQL...</description>
      <pubDate>Fri, 17 Jan 2003 09:56:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/mysql-is-good-except-for/m-p/2883748#M3398</guid>
      <dc:creator>Michael Armbrecht</dc:creator>
      <dc:date>2003-01-17T09:56:19Z</dc:date>
    </item>
    <item>
      <title>Re: MySQL is good, except for....</title>
      <link>https://community.hpe.com/t5/operating-system-linux/mysql-is-good-except-for/m-p/2883749#M3399</link>
      <description>Can't you just... bypass the problem ?&lt;BR /&gt;I've been using Mysql for eons, along with MS SQL server (which uses subqueries), and when on Mysql, this problem never affected my queries.&lt;BR /&gt;Can't you do a sort of SELECT * FROM orders, snum FROM stuff, WHERE orders.sth=stuff=sthelse AND otherarg ?&lt;BR /&gt;Jerome</description>
      <pubDate>Fri, 17 Jan 2003 10:06:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/mysql-is-good-except-for/m-p/2883749#M3399</guid>
      <dc:creator>Jerome Henry</dc:creator>
      <dc:date>2003-01-17T10:06:45Z</dc:date>
    </item>
    <item>
      <title>Re: MySQL is good, except for....</title>
      <link>https://community.hpe.com/t5/operating-system-linux/mysql-is-good-except-for/m-p/2883750#M3400</link>
      <description>Sorry, folks, this was supposed to be a reply to someone else's question---don't know how it became a new topic. Please disregard.</description>
      <pubDate>Fri, 17 Jan 2003 15:45:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/mysql-is-good-except-for/m-p/2883750#M3400</guid>
      <dc:creator>dan dobbs</dc:creator>
      <dc:date>2003-01-17T15:45:14Z</dc:date>
    </item>
    <item>
      <title>Re: MySQL is good, except for....</title>
      <link>https://community.hpe.com/t5/operating-system-linux/mysql-is-good-except-for/m-p/2883751#M3401</link>
      <description>MySQL is quite nice for lots of general stuff indeed. As for subselects, MySQL doesn't support this. Yet. It's planned and it's already implemented in development version 4.1.&lt;BR /&gt;&lt;BR /&gt;Most of the time, however, you can circumvent a subselect by formulating your query in a different way. Hints about this are on the MySQL-site and probably on lots of other places too.&lt;BR /&gt;&lt;BR /&gt;If you really need subselects (and other SQL-stuff like transactions and views), you could take a look at PostgreSQL (&lt;A href="http://www.postgresql.org)." target="_blank"&gt;http://www.postgresql.org).&lt;/A&gt; PostgreSQL is a lot bigger than MySQL however, and for a reason ;)&lt;BR /&gt;&lt;BR /&gt;Kind regards,&lt;BR /&gt;&lt;BR /&gt;Hans</description>
      <pubDate>Wed, 05 Mar 2003 12:40:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/mysql-is-good-except-for/m-p/2883751#M3401</guid>
      <dc:creator>Hans van Zijst</dc:creator>
      <dc:date>2003-03-05T12:40:30Z</dc:date>
    </item>
  </channel>
</rss>

