Message-ID: <3B0060E8.EDCF98D7@darold.net>
Date: Tue, 15 May 2001 00:49:12 +0200
From: Gilles DAROLD <gilles@darold.net>
Reply-To: gilles@darold.net
MIME-Version: 1.0
To: Simon Crute <simon-news@nospam.geordie.demon.co.uk>
CC: pgsql-general@postgresql.org
Subject: Re: Re: case sensitivity
References: <22535.989723392@sss.pgh.pa.us>
	<989749499.4806.0.nnrp-08.9e981bad@news.demon.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Simon Crute wrote:

> If anyone's interested,
> I found the answer to my first question buried in the DBI docs
> (fetch_hashref("NAME_uc") if anyone's interested)
>
> With regards to case
> > AFAIK we're exactly as picky about it as Oracle, just in the opposite
> > direction.
>
> I think there's some differences in function names. In oracle I think you
> can get away with count(), or COUNT(), in postgres it has to be COUNT(), but
> this was probably going through the perl DBI, so that may have been
> complicating things.

Oracle doesn't care about case sensitive in queries, Postgres too if you don't
quote tablename or columnname at creation time. If you use quote and upercase
at creation time you may quote it as well in you're queries. Function can be
lower
or upper case it doesn't matter at least in PostgreSQL 7.0.3.

SELECT COUNT(*) FROM "T_USERPREF";
select count(*) from "T_USERPREF";

Works well.

But you want columname returned as uppercase and you find the way...