Re: drupal.org MySQL database issues

From: "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>
To: "Brian Hurt" <bhurt(at)janestcapital(dot)com>
Cc: "John DeSoi" <desoi(at)pgedit(dot)com>, pgsql-advocacy(at)postgresql(dot)org
Subject: Re: drupal.org MySQL database issues
Date: 2007-05-16 13:47:42
Message-ID: 36e682920705160647j3158d112p7314d8ba36443956@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

On 5/16/07, Brian Hurt <bhurt(at)janestcapital(dot)com> wrote:
> I have never understood the purpose of having more than one "backend" to
> the database. As near as I can figure, it's only purpose is to allow
> people to pick the wrong one.

Umm, because MySQL copied others... like POSTGRES (which was one of
the first to implement that concept). While their multiple storage
manager implementation lacks several items key to good performance, it
does give the end-user a choice to implement the one that fits their
particular needs and workload.

MySQL is *not* the only database which supports multiple storage engines.

--
Jonah H. Harris, Software Architect | phone: 732.331.1324
EnterpriseDB Corporation | fax: 732.331.1301
33 Wood Ave S, 3rd Floor | jharris(at)enterprisedb(dot)com
Iselin, New Jersey 08830 | http://www.enterprisedb.com/

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Leif B. Kristensen 2007-05-16 13:56:51 Re: drupal.org MySQL database issues
Previous Message Brian Hurt 2007-05-16 13:37:54 Re: drupal.org MySQL database issues