MySQL RANT

[rlk-FrUbXkNCsVf2fBVCVOL8/A at public.gmane.org (Robert L Krawitz)]

   Date: Fri, 8 Jun 2007 23:11:17 -0400 (EDT)
   From: markw-FJ05HQ0HCKaWd6l5hS35sQ at public.gmane.org

   > Query planners and join strategies are nice if your application
   > is going to put heavy demands on the relevant parts of the
   > database.  If you have a very small database that isn't going to
   > grow very much in size or complexity, and you don't need ACID
   > compliance, transactional semantics, and all that, what's the
   > problem?

   Well, here's the thing, based on technical merit, what makes MySQL
   a good decision over something like PostgreSQL? My statement still
   stands, a professional makes decisions based on merit and can
   document the decision process. Describe *any* process where MySQL
   seems like a good idea, again, based on merit.

I didn't say "technical" merit.  Good engineering isn't simply picking
the best technical solution; it's picking the best solution *for the
job*.  There may be other issues -- resource consumption,
configuration, time to deployment, etc -- that may outweigh the purely
technical merits.  Your blanket implication that MySQL is so inferior
that its use is prima facie evidence of incompetence is a rather
strong statement.

I haven't installed or configured databases, so I can't actually speak
to the merits of MySQL vs. PostgreSQL.

-- 
Robert Krawitz                                     <rlk-FrUbXkNCsVf2fBVCVOL8/A at public.gmane.org>

Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom -- mail lpf-BtI67efEdsDk1uMJSBkQmQ at public.gmane.org
Project lead for Gutenprint   --    http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.