Subject: Re: What can we learn from MySQL?
From: Rod Taylor <pg@rbt.ca>
To: Jeff Davis <jdavis-pgsql@empires.org>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>,
	Postgresql Advocacy <pgsql-advocacy@postgresql.org>
In-Reply-To: <1082707709.32307.1127.camel@jeff>
References: <200404230409.i3N49jC02890@candle.pha.pa.us>
	<1082707709.32307.1127.camel@jeff>
Content-Type: text/plain
Message-Id: <1082730417.95625.41.camel@jester>
Mime-Version: 1.0
Date: Fri, 23 Apr 2004 10:26:58 -0400
Content-Transfer-Encoding: 7bit

> One common thing people talk about is ease of use. However that puzzles
> me, since it takes all of (about) three commands to install postgresql
> and log into the database for the first time. I use debian, so it
> amounts to "apt-get install", su to "postgres" and "psql template1".

My present theory is that most users make the decision regarding ease of
use before even installing the software.

If you look at the MySQL website within 1 or 2 clicks, you know that
there is a gui for queries, a gui for administration, drivers or
interfaces for many programming langauges. They have GIS, Unicode, full
text searching, multi-master replication, ANSI compliance, etc.

Not that all of those items are necessarily true, but that is what the
user believes.


In contrast, from the PostgresSQL website I know PostgreSQL can deal
with a large dataset, has lots of backend features, supports many
languages. Looking hard enough you might find a link to the
pgreplication which currently has the goal of integrating with
PostgreSQL 7.2 ;)

You don't learn anything about the GUIs (any of them) within the first
couple of clicks. Since many users (even linux users) associate command
lines with difficulty of use, the first impression is that PostgreSQL is
difficult to use.