X-Original-To: pgsql-advocacy-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id CE7CFD1BA2E for ; Fri, 23 Apr 2004 04:11:14 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 96672-02 for ; Fri, 23 Apr 2004 04:11:14 -0300 (ADT) Received: from latenight.fiasco.org.il (latenight.fiasco.org.il [192.117.122.39]) by svr1.postgresql.org (Postfix) with SMTP id 28599D1B8CA for ; Fri, 23 Apr 2004 04:11:12 -0300 (ADT) Received: (qmail 23256 invoked from network); 23 Apr 2004 07:11:12 -0000 X-Scanned-By: AMaViS-ng at latenight.fiasco.org.il Received: from unknown (HELO shemesh.biz) (192.117.102.130) by latenight.fiasco.org.il with SMTP; 23 Apr 2004 07:11:11 -0000 Message-ID: <4088C18F.9090807@shemesh.biz> Date: Fri, 23 Apr 2004 10:11:11 +0300 From: Shachar Shemesh Organization: Lingnu Open Source Consulting User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040413 Debian/1.6-5 X-Accept-Language: en, he MIME-Version: 1.0 To: Bruce Momjian Cc: PostgreSQL-development , PostgreSQL advocacy Subject: Re: [HACKERS] What can we learn from MySQL? References: <200404230409.i3N49jC02890@candle.pha.pa.us> In-Reply-To: <200404230409.i3N49jC02890@candle.pha.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200404/208 X-Sequence-Number: 4180 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=185&tid=187&tid=198 > >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/