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 6E93AD1D06E for ; Fri, 23 Apr 2004 08:45:56 -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 75873-08 for ; Fri, 23 Apr 2004 08:45:58 -0300 (ADT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id C4721D1C4EC for ; Fri, 23 Apr 2004 08:45:54 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i3NBjthE020460; Fri, 23 Apr 2004 07:45:55 -0400 (EDT) To: Dennis Bjorklund Cc: Shachar Shemesh , Bruce Momjian , PostgreSQL-development , PostgreSQL advocacy Subject: Re: [HACKERS] What can we learn from MySQL? In-reply-to: References: Comments: In-reply-to Dennis Bjorklund message dated "Fri, 23 Apr 2004 11:22:33 +0200" Date: Fri, 23 Apr 2004 07:45:54 -0400 Message-ID: <20459.1082720754@sss.pgh.pa.us> From: Tom Lane 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/142 X-Sequence-Number: 4114 Dennis Bjorklund writes: > On Fri, 23 Apr 2004, Shachar Shemesh wrote: >> 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. > I would love if someone fixed pg so that one can get the standard > behaviour. It would however have to be a setting that can be changed so we > are still backward compatible. Yes. There have been repeated discussions about how to do this, but no one's come up with a solution that seems workable. See the archives if you care. For the foreseeable future, backwards compatibility is going to trump standards compliance on this point. That doesn't mean we don't care about compliance; it does mean that it is not the *only* goal. I find it a bit odd to be debating this point in this thread, seeing that one of the big lessons I draw from MySQL is "standards compliance does not matter"... regards, tom lane