From: | Robert L Mathews <lists(at)tigertech(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: I am being interviewed by OReilly |
Date: | 2002-07-05 17:14:36 |
Message-ID: | 20020705171435.BDF803FC45D@mail1.tigertech.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
At 7/5/02 3:33 AM, Tom Lane wrote:
>I've heard a number of people opine that we should go back to just plain
>'Postgres', which is pronounceable by the uninitiate, and besides which
>that's what we use informally most of the time. 'PostgreSQL' is about
>as marketing-unfriendly a name as you could easily find...
What's even worse is that when you do a search for a particular piece of
information about PostgreSQL, you have to do the search twice, because
you don't know whether the Web page or message that you're looking for
would have referred to it as "Postgres" or "PostgreSQL".
Heck, I can never even remember if the username created by the install is
"postgres" or "postgresql".
The fact that so many people don't use the full name "PostgreSQL" seems
to me to be an indication in and of itself that something is wrong with
it. And the fact that they use "Postgres" instead is an indication of
what it should be called (the full official name could be "Postgres SQL
Server").
I see the point of having "SQL" in the name -- it theoretically lets
people know what it does, like "MySQL" -- but in practice, the
disadvantages of "PostgreSQL" seem to far outweigh that benefit.
------------------------------------
Robert L Mathews, Tiger Technologies
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Wollny | 2002-07-05 17:20:05 | Performance of ODBC-Driver /w IIS5.0/ColdFusion |
Previous Message | Stephan Szabo | 2002-07-05 17:12:59 | Re: explicit cast error |