From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-advocacy(at)postgresql(dot)org |
Subject: | Re: drupal.org MySQL database issues |
Date: | 2007-05-16 17:55:03 |
Message-ID: | 200705161055.03231.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
Brian, Jeff,
> > 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.
Well, the real purpose of the backend storage engines is to make MySQL into
more than one kind of database. MyISAM is for a single-user DB, InnoDB is
for transactions, NDB is clustered & object, Ericsson is telecom, MemDB is
in-memory, etc. It makes up for the fact that MySQL does not excel in any
one database category if it is percieved to be adequate in all categories.
> In MySQL, changing the "storage engine" can break user queries and
> always requires a full data migration to the new format.
Sure, but MySQL users and potential users don't perceive it that way -- they
encounter the problems only long after they've made hard-to-revoke decisions
to adopt MySQL. MySQL is still much, much better at marketing than we are.
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Ned Lilly | 2007-05-16 18:51:35 | Re: drupal.org MySQL database issues |
Previous Message | Jeff Davis | 2007-05-16 16:56:07 | Re: drupal.org MySQL database issues |