Обсуждение: Turning of case sensitivity for identifiers?

Поиск
Список
Период
Сортировка

Turning of case sensitivity for identifiers?

От
"Joost Kraaijeveld"
Дата:
Hi all,

Is it possible to turn of the case sensitivity for tables and columns in queries (to all CAPS)?  I have a (closed
source)tool that I have to use (Clarion) that generates the queries and I cannot change the way the tool generates the
queries.

Groeten,

Joost Kraaijeveld
Askesis B.V.
Molukkenstraat 14
6524NB Nijmegen
tel: 024-3888063 / 06-51855277
fax: 024-3608416
e-mail: J.Kraaijeveld@Askesis.nl
web: www.askesis.nl

Re: Turning of case sensitivity for identifiers?

От
Peter Eisentraut
Дата:
Am Mittwoch, 14. Juli 2004 10:55 schrieb Joost Kraaijeveld:
> Is it possible to turn of the case sensitivity for tables and columns in
> queries (to all CAPS)?  I have a (closed source) tool that I have to use
> (Clarion) that generates the queries and I cannot change the way the tool
> generates the queries.

The table and column names are not actually case sensitive; they are just
folded to lower case while you apparently expect upper case.  If you write
the names the same way in each command, there should not be a problem.  What
problem are you actually seeing?

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

Re: Turning of case sensitivity for identifiers?

От
"Joost Kraaijeveld"
Дата:
Hi Peter,

Peter Eisentraut schreef:
> The table and column names are not actually case sensitive;
> they are just folded to lower case while you apparently expect upper case.
I am unsure of the translation of "fold". Is that the same as translate? Does that mean that if Postgresql get a query
withoutquotes it translates the schema/column/table to lower case automatically? 


> If you write the names the same way in each command, there should not be a
> problem.
I cannot see how Clarion creates the queries. I have to deduct it from a log file that does not show me the query as-is
butgives a "user friendly" translation of the query, without any quotes. 

> What problem are you actually seeing?
Clarion checks whether the table is valid. For that, it seems to do an ODBC SQLColumns which returns the
schema/table/columnname in lower case while Clarino is expecting it to be uppercase. Hence it says that the table is
notvalid (it seems to find the table but not the columns). On a DB2 database (that has all caps names) it works. 


Groeten,

Joost Kraaijeveld
Askesis B.V.
Molukkenstraat 14
6524NB Nijmegen
tel: 024-3888063 / 06-51855277
fax: 024-3608416
e-mail: J.Kraaijeveld@Askesis.nl
web: www.askesis.nl

Re: Turning of case sensitivity for identifiers?

От
Stephan Szabo
Дата:
On Wed, 14 Jul 2004, Joost Kraaijeveld wrote:

> Is it possible to turn of the case sensitivity for tables and columns in
> queries (to all CAPS)?  I have a (closed source) tool that I have to use
> (Clarion) that generates the queries and I cannot change the way the
> tool generates the queries.

It's not currently possible to turn off case folding or to force spec
complient upper case folding. You may want to look through the archives
for the discussions if you wish to add something.


Re: Turning of case sensitivity for identifiers?

От
Tom Lane
Дата:
"Joost Kraaijeveld" <J.Kraaijeveld@Askesis.nl> writes:
> I cannot see how Clarion creates the queries.

That's easily fixed.  Turn on log_statement in postgresql's
configuration file and look at the server-side log to see what Clarion
is sending.

            regards, tom lane