public inbox for [email protected]
help / color / mirror / Atom feedFrom: Robert Treat <[email protected]>
To: Shachar Shemesh <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Cc: PostgreSQL advocacy <[email protected]>
Subject: Re: Do we prefer software that works or software that looks good?
Date: Sat, 24 Apr 2004 09:09:46 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
On Saturday 24 April 2004 08:09, Shachar Shemesh wrote:
> Robert Treat wrote:
> > Anyone who has studied software useability will
> >know that uppercase should, in general, be avoided as it hurts
> > readability.
>
> You convinced me! let's change the SQL standard.
>
We plan to, right after we have PostgreSQL achieve world domination. But we
can't abondon lower case now or it will weaken the argument when that time
comes. :-)
>
> Ok. I'm willing to change the subject to "are hurting eyes due to
> uppercase preferable to changing lots of code when migrating to PG from
> other database due to standard incomplience", if it would make you feel
> better.
>
ouch. s/code when/code from crappily written apps when/ :-)
> The point is that I am not against lower case, or pro uppercase. I HATE
> uppercase. I do think, however, that standards should be followed. The
> question is, when all is said and done, which is more useable. A DB that
> presents unquoted identifiers as uppercase, or one that allows easier
> migration of client apps from other DBs.
>
IMHO apps that apply quoted identifiers willy nilly are busted anyway, and it
is only by coincidence that they work on other databases if they work at all.
(And it's by extremely unfortunate coincidence that they might be spec
complient in that behavior.. but hey.)
Oh well... let's see if we can find a way to support both...
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
view thread (144+ 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]
Subject: Re: Do we prefer software that works or software that looks good?
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