Date: Fri, 23 Apr 2004 11:22:33 +0200 (CEST)
From: Dennis Bjorklund <db@zigo.dhs.org>
To: Shachar Shemesh <psql@shemesh.biz>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>,
	PostgreSQL advocacy <pgsql-advocacy@postgresql.org>
Subject: Re: [HACKERS] What can we learn from MySQL?
In-Reply-To: <4088C18F.9090807@shemesh.biz>
Message-ID: <Pine.LNX.4.44.0404231117270.4551-100000@zigo.dhs.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT

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.

> that even if I write a patch to start migration, I'm not likely to get
> it in.

Just changing to uppercase would break old code so such a patch should not
just be commited. But would people stop a patch that is backward
compatible (in the worst case a setting during initdb)? I'm not so sure
they will.

--
/Dennis Björklund