public inbox for [email protected]
help / color / mirror / Atom feedFrom: Andrew Sullivan <[email protected]>
To: PostgreSQL-development <[email protected]>
To: PostgreSQL advocacy <[email protected]>
Subject: Re: [HACKERS] What can we learn from MySQL?
Date: Sat, 24 Apr 2004 13:46:41 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <1082735128.22969.1106.camel@camel>
References: <[email protected]>
<1082735128.22969.1106.camel@camel>
On Fri, Apr 23, 2004 at 11:45:28AM -0400, Robert Treat wrote:
> lower will now simply be folder upper. the only people who will have a
> problem are those who quote on one end but not the other, which is bad
> practice anyways... so i would say if your serious about it, make the
> patch as GUC "case_folding" for upper or lower and get a taste for what
> breaks inside the db.
If it were that easy, it wouldn't matter, right? That is, if you had
a system which was either consistently quoted or consistently
unquoted, then you'd never run into the problem of the upper-or-lower
question.
It's precisely _because_ systems often have been maintained by
various cranks for 20 years that it's a problem. One guy thinks
quoting is stupid. Another thinks that if you don't quote, you're
asking for trouble, A third has been rigourous in following the
quoting convention he learned in his last job. The ship date is
three weeks away, and there are 802 "P1" bugs filed. What chance do
you think there is that someone is going to scrub all the checkins of
quotes (or apply them carefully)? This is _exactly_ why standards
compliance for this stuff matters, and why backward comaptibility is
also a top priority.
A
--
Andrew Sullivan | [email protected]
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]
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