public inbox for [email protected]
help / color / mirror / Atom feedFrom: Dennis Bjorklund <[email protected]>
To: Shachar Shemesh <[email protected]>
Cc: 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 11:22:33 +0200 (CEST)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
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
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], [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