> -----Original Message-----
> From: Stephan Szabo [mailto:[EMAIL PROTECTED]
> Sent: 24 April 2004 08:43
> To: Shachar Shemesh
> Cc: Tom Lane; Robert Treat; Dennis Bjorklund; Bruce Momjian;
> PostgreSQL-development; PostgreSQL advocacy
> Subject: Re: [HACKERS] Do we prefer software that works or
> software that looks good?
>
>
> 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.
I'm unfamiliar with the code involved so this may be a waste of
bandwidth, but it seems to me that any selection of upper or lower case
folding should be done on a per-database basis - probably specified in
the create database statement, and flagged in pg_database. If its done
per-database then any issues of "FOO" == foo go away unless someone
loads a lowercase dump into an uppercase database - in which case it's
up to them to resolve any conflicts prior to loading the dump file.
Regards, Dave.
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
