public inbox for [email protected]  

help / color / mirror / Atom feed

From: Shachar Shemesh <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Cc: PostgreSQL advocacy <[email protected]>
Subject: Re: [HACKERS] What can we learn from MySQL?
Date: Fri, 23 Apr 2004 10:11:11 +0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

Bruce Momjian wrote:

>Here is a blog about a recent MySQL conference with title, "Why MySQL
>Grew So Fast":
>
>	http://www.oreillynet.com/pub/wlg/4715
>
>and a a Slashdot discussion about it:
>
>	http://developers.slashdot.org/article.pl?sid=04/04/20/2229212&mode=nested&tid=137&tid=1...
>
>My question is, "What can we learn from MySQL?"  I don't know there is
>anything, but I think it makes sense to ask the question.
>
>Questions I have are:
>
>	o  Are we marketing ourselves properly?
>	o  Are we focused enough on ease-of-use issues?
>	o  How do we position ourselves against a database that some
>	   say is "good enough" (MySQL), and another one that some
>	   say is "too much"  (Oracle)
>	o  Are our priorities too technically driven?
>	
>  
>
Do we care enough about interoperability?

When I ask about non-standard complience of Pg (turning unquoted 
identifiers to lowercase instead of uppercase, violating the SQL 
standard, and requring an expensive rewrite of clients), and I get the 
answer "uppercase is ugly", I think something is wrong.

To be fair, I got a fair amount of legitimate problems with MIGRATING to 
standard compliency. I find these issues legitimate, though solveable. 
Getting a "we prefer lowercase to the standard", however, means to me 
that even if I write a patch to start migration, I'm not likely to get 
it in.

          Shachar

-- 
Shachar Shemesh
Lingnu Open Source Consulting
http://www.lingnu.com/

view thread (145+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: [HACKERS] What can we learn from MySQL?
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox