public inbox for [email protected]  

help / color / mirror / Atom feed

From: Stephan Szabo <[email protected]>
To: Shachar Shemesh <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Robert Treat <[email protected]>
Cc: Dennis Bjorklund <[email protected]>
Cc: Bruce Momjian <[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 00:43:25 -0700 (PDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<1082735128.22969.1106.camel@camel>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Sat, 24 Apr 2004, Shachar Shemesh wrote:

> Tom Lane wrote:
> >So what I'm holding out for is a design that lets me continue to see the
> >current behavior if I set a GUC variable that says that's what I want.
> >
> >This seems possible (not easy, but possible) if we are willing to
> >require the choice to be made at compile time ... but that sounds too
> >restrictive to satisfy anybody ... what we need is a design that
> >supports such a choice per-session, and I dunno how to do that.
> >
> >
> In other words, you are going to reject the simpler solutions that treat
> this as a transition problem, because of asthetic issue? Not even
> program design issue, mind you. Sounds strange to me, and also pretty
> much guarentees that this will never happen. That would be a shame.

[ Tom, we know your opinion on the first part of the next paragraph, so
you don't need to reply to that part. ;) ]

Are we going to get rid of the current behavior entirely? If so, how are
we going to handle issues like current databases with names like foo and
"FOO" (and what if the name was given as "foo")? If not, when can one set
the folding options and how do we (in the long term) make the database
work properly in both settings. Things like "don't worry about the catalog
entries" don't fly when your standard functions are defined and
looked up there.

Depending on the answers to the above, we need to think about things like
the transitional plans put forth. Do these plans actually help transition
things. The fold up and down compare one then the other on a failure of
the first may be fairly invasive changes, still has problems when quotes
are used inconsistently and can also silently change behavior from old
versions (on that database mentioned above, what does select * from foo
do, is it the same as before?). These may or may not be huge issues and it
may or may not be easily solvable, but these things need to be figured out
IMHO before something can be considered a solution.

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], [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